CVE-2023-39615

Exp

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.

Published: 2023-08-29 Last update: 2025-11-03 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2023-39615 is rated Exploit Available (57.9/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.67%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2023-39615

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2023-39615

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.13% 0.67% +0.54%
2 2026-04-09 0.15% 0.13% -0.03%
3 2026-04-05 — 0.15% —

Full EPSS history (12 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2023-39615

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 3.6 [email protected]

Weakness enumeration for CVE-2023-39615

OS Trackers for CVE-2023-39615

vendor priority summary link
debian not yet assigned CVE-2023-39615 not yet assigned priority: Debian including 1 source packages (libxml2), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2023-39615
redhat medium — https://access.redhat.com/security/cve/CVE-2023-39615
suse medium CVE-2023-39615 severity moderate: SUSE including 379 source package names (0.23.0.3.2.527:libxml2-2-2.9.7-150000.3.60.1, 0.23:libxml2-2-2.10.3-150500.5.8.1, …), 940 product×package rows across 358 product lines (Container bci/bci-init, Container bci/bci-sle15-kernel-module-devel, … (358 product lines)): Fixed 765, Known Affected 175. https://www.suse.com/security/cve/CVE-2023-39615/
ubuntu medium CVE-2023-39615 medium priority: Ubuntu including 1 source packages (libxml2), 8 status rows across 8 suites (bionic, focal, jammy, lunar, mantic, trusty, upstream, xenial): not-affected 7, needs-triage 1. https://ubuntu.com/security/CVE-2023-39615

Affected software / configurations for CVE-2023-39615

Vendor Product Version Raw CPE
xmlsoft libxml2 2.11.0 cpe:2.3:a:xmlsoft:libxml2:2.11.0:*:*:*:*:*:*:*

References for CVE-2023-39615

cvelogic Threat Intelligence