Skip to content
Noroxi
NVD / CVE Program· CNA mitre

CVE-2023-39615: Xmlsoft Libxml2 v2.11.0 was discovered to contain an out-of-bounds read via the xmlSAX2StartElement() function at /libxml2/SAX2.c.

Noroxi assessment

Priority: Monitor (action score 26/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1% (FIRST EPSS); higher than 64.9% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
  • Fixed version: libxml2 (AlmaLinux:8) 2.9.7-18.el8_9; libxml2-devel (AlmaLinux:8) 2.9.7-18.el8_9; python3-libxml2 (AlmaLinux:8) 2.9.7-18.el8_9.

Low priority for now. Upgrade to libxml2 (AlmaLinux:8) 2.9.7-18.el8_9; libxml2-devel (AlmaLinux:8) 2.9.7-18.el8_9; python3-libxml2 (AlmaLinux:8) 2.9.7-18.el8_9 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Xmlsoft Libxml2 v2.11.0 was discovered to contain an out-of-bounds read via the xmlSAX2StartElement() function at /libxml2/SAX2.c. This vulnerability allows attackers to cause a Denial of Service (DoS) via supplying a crafted XML file. NOTE: the vendor's position is that the product does not support the legacy SAX1 interface with custom callbacks; there is a crash even without crafted input.

MediumCVSS 6.5 · v3.1—No exploit Fix available
Published
Aug 29, 2023
Updated
Oct 15, 2026
EPSS
1.0% · 64th percentile

Report tools

JSON

Action score

26

Monitor

Low priority for now.

CVSS
26 / 40 · 6.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.0%

CISA SSVC decision

Exploitation
proof of concept
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-39615

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for xmlsoft records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
xmlsoftlibxml2

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • xmlsoft libxml22.11.0

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8libxml2before 2.9.7-18.el8_92.9.7-18.el8_9
AlmaLinux:8libxml2-develbefore 2.9.7-18.el8_92.9.7-18.el8_9
AlmaLinux:8python3-libxml2before 2.9.7-18.el8_92.9.7-18.el8_9
AlmaLinux:9libxml2before 2.9.13-5.el9_32.9.13-5.el9_3
AlmaLinux:9libxml2-develbefore 2.9.13-5.el9_32.9.13-5.el9_3
AlmaLinux:9python3-libxml2before 2.9.13-5.el9_32.9.13-5.el9_3
Debian:11libxml2before 2.9.10+dfsg-6.7+deb11u62.9.10+dfsg-6.7+deb11u6
Debian:12libxml2before 2.9.14+dfsg-1.3~deb12u22.9.14+dfsg-1.3~deb12u2
Debian:13libxml2before 2.12.7+dfsg+really2.9.14-12.12.7+dfsg+really2.9.14-1
openSUSE:Leap 15.4libxml2before 2.9.14-150400.5.22.12.9.14-150400.5.22.1
openSUSE:Leap 15.4libxml2-pythonbefore 2.9.14-150400.5.22.12.9.14-150400.5.22.1
openSUSE:Leap 15.4python-libxml2-pythonbefore 2.9.7-150000.3.60.12.9.7-150000.3.60.1
openSUSE:Leap 15.5libxml2before 2.10.3-150500.5.8.12.10.3-150500.5.8.1
openSUSE:Leap 15.5libxml2-pythonbefore 2.10.3-150500.5.8.12.10.3-150500.5.8.1
openSUSE:Tumbleweedlibxml2before 2.10.4-3.12.10.4-3.1
Red Hat:enterprise_linux:8::appstreamlibxml2-debuginfobefore 0:2.9.7-18.el8_90:2.9.7-18.el8_9
Red Hat:enterprise_linux:8::appstreamlibxml2-debugsourcebefore 0:2.9.7-18.el8_90:2.9.7-18.el8_9
Red Hat:enterprise_linux:8::appstreamlibxml2-develbefore 0:2.9.7-18.el8_90:2.9.7-18.el8_9
Red Hat:enterprise_linux:8::appstreampython3-libxml2-debuginfobefore 0:2.9.7-18.el8_90:2.9.7-18.el8_9
Red Hat:enterprise_linux:8::baseoslibxml2before 0:2.9.7-18.el8_90:2.9.7-18.el8_9
Red Hat:enterprise_linux:8::baseospython3-libxml2before 0:2.9.7-18.el8_90:2.9.7-18.el8_9
Red Hat:enterprise_linux:9::appstreamlibxml2-debuginfobefore 0:2.9.13-5.el9_30:2.9.13-5.el9_3
Red Hat:enterprise_linux:9::appstreamlibxml2-debugsourcebefore 0:2.9.13-5.el9_30:2.9.13-5.el9_3
Red Hat:enterprise_linux:9::appstreamlibxml2-develbefore 0:2.9.13-5.el9_30:2.9.13-5.el9_3

+25

Same product

xmlsoft: all records

Other highest-scoring records for the same primary product.

  • CVE-2008-3529Heap-based buffer overflow in the xmlParseAttValueComplex function in parser.c in libxml2 before 2.7.0 allows context-dependent attackers to
    47Plan
  • CVE-2017-7376Buffer overflow in libxml2 allows remote attackers to execute arbitrary code by leveraging an incorrect limit for port values when handling
    46Plan
  • CVE-2022-40303An issue was discovered in libxml2 before 2.10.3.
    42Plan

Published before and after this one in the same product

  • ← EarlierCVE-2023-28484Apr 24, 2023 · In libxml2 before 2.10.4, parsing of certain invalid XSD schemas can lead to a NULL pointer dereference and subsequently a segfault.
    26Monitor
  • ← EarlierCVE-2023-29469Apr 24, 2023 · An issue was discovered in libxml2 before 2.10.4.
    26Monitor
  • Later →CVE-2023-45322Oct 6, 2023 · libxml2 through 2.11.5 has a use-after-free that can only occur after a certain memory allocation fails.
    26Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
almalinux:libxml22.9.13-5.el9_3 · AlmaLinux:9Package registry (OSV)
almalinux:libxml2-devel2.9.13-5.el9_3 · AlmaLinux:9Package registry (OSV)
almalinux:python3-libxml22.9.13-5.el9_3 · AlmaLinux:9Package registry (OSV)
debian:libxml22.9.14+dfsg-1.3~deb12u2 · Debian:12Package registry (OSV)
opensuse:libxml22.10.3-150500.5.8.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:libxml2-python2.10.3-150500.5.8.1 · openSUSE:Leap 15.5Package registry (OSV)
opensuse:python-libxml2-python2.9.7-150000.3.60.1 · openSUSE:Leap 15.4Package registry (OSV)
red hat:libxml20:2.9.7-16.el8_8.2 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:libxml2-debuginfo0:2.9.7-16.el8_8.2 · Red Hat:rhel_eus:8.8::appstreamPackage registry (OSV)
red hat:libxml2-debugsource0:2.9.7-16.el8_8.2 · Red Hat:rhel_eus:8.8::appstreamPackage registry (OSV)
red hat:libxml2-devel0:2.9.7-16.el8_8.2 · Red Hat:rhel_eus:8.8::appstreamPackage registry (OSV)
red hat:python3-libxml20:2.9.7-16.el8_8.2 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:python3-libxml2-debuginfo0:2.9.7-16.el8_8.2 · Red Hat:rhel_eus:8.8::appstreamPackage registry (OSV)
rocky linux:libxml20:2.9.7-18.el8_9 · Rocky Linux:8Package registry (OSV)
suse:libxml22.10.3-150500.5.8.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP5Package registry (OSV)
suse:libxml22.9.4-46.65.1 · SUSE:Linux Enterprise Software Development Kit 12 SP5Package registry (OSV)
suse:libxml2-python2.10.3-150500.5.8.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP5Package registry (OSV)
suse:python-libxml22.9.4-46.65.1 · SUSE:Linux Enterprise Server 12 SP5Package registry (OSV)
suse:python-libxml2-python2.9.7-150000.3.60.1 · SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSSPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-119 · Improper Restriction of Operations within the Bounds of a Memory Buffer

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records