CVE-2023-45322

libxml2 through 2.11.5 has a use-after-free that can only occur after a certain memory allocation fails. This occurs in xmlUnlinkNode in tree.c. NOTE: the vendor's position is "I don't think these issues are critical enough to warrant a CVE ID ... because an attacker typically can't control when memory allocations fail."

Published: 2023-10-06 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-45322 is rated Moderate Risk (45.1/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 0.83%). Review affected assets and schedule remediation.

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

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

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.08% 0.83% +0.75%
2 2025-11-21 0.56% 0.08% -0.48%
3 2025-11-18 — 0.56% —

Full EPSS history (15 records total)

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

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-45322

OS Trackers for CVE-2023-45322

vendor priority summary link
alpine — CVE-2023-45322: 1 source package rows (libxml2); 3 state rows across 3 repos (3.17-main, 3.18-main, edge-main); fixed 0, open 3. https://security.alpinelinux.org/vuln/CVE-2023-45322
debian not yet assigned CVE-2023-45322 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-45322
gentoo normal CVE-2023-45322: 1 GLSA(s) (202402-11), 1 atom(s) (dev-libs/libxml2); latest impact normal. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2023-45322
redhat low — https://access.redhat.com/security/cve/CVE-2023-45322
suse medium CVE-2023-45322 severity moderate: SUSE including 358 source package names (0.23:libxml2-2-2.10.3-150500.5.11.1, 0.3.2-1.2:libxml2-2-2.10.3-150500.5.11.1, …), 811 product×package rows across 319 product lines (Container bci/bci-init, Container bci/bci-sle15-kernel-module-devel, … (319 product lines)): Fixed 626, Known Affected 185. https://www.suse.com/security/cve/CVE-2023-45322/
ubuntu medium CVE-2023-45322 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-45322

Affected software / configurations for CVE-2023-45322

Vendor Product Version Raw CPE
xmlsoft libxml2 <= 2.11.5 cpe:2.3:a:xmlsoft:libxml2:*:*:*:*:*:*:*:*

References for CVE-2023-45322

cvelogic Threat Intelligence