CVE-2016-9596

libxml2, as used in Red Hat JBoss Core Services and when in recovery mode, allows context-dependent attackers to cause a denial of service (stack consumption) via a crafted XML document. NOTE: this vulnerability exists because of an incorrect fix for CVE-2016-3627.

Published: 2018-08-16 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2016-9596 is rated Moderate Risk (47.5/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 1.08%). 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-2016-9596

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-07-02 0.91% 1.08% +0.17%
2 2026-06-15 0.67% 0.91% +0.23%
3 2025-03-30 — 0.67% —

Full EPSS history (7 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2016-9596

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]
4.3 2.0 MEDIUM
AV:N/AC:M/Au:N/C:N/I:N/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.6 2.9 [email protected]

Weakness enumeration for CVE-2016-9596

OS Trackers for CVE-2016-9596

vendor priority summary link
debian unimportant CVE-2016-9596 unimportant 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-2016-9596
redhat medium — https://access.redhat.com/security/cve/CVE-2016-9596
suse medium CVE-2016-9596 severity moderate: SUSE including 5 source package names (libxml2, libxml2-2, libxml2-2-32bit, libxml2-doc, libxml2-tools), 73 product×package rows across 17 product lines (HPE Helion OpenStack 8, SUSE Linux Enterprise High Performance Computing 12 SP5, … (17 product lines)): Known Not Affected 73. https://www.suse.com/security/cve/CVE-2016-9596/
ubuntu low CVE-2016-9596 low priority: Ubuntu including 1 source packages (libxml2), 5 status rows across 5 suites (precise, trusty, upstream, xenial, yakkety): not-affected 4, needs-triage 1. https://ubuntu.com/security/CVE-2016-9596

Affected software / configurations for CVE-2016-9596

Vendor Product Version Raw CPE
redhat jboss_core_services — cpe:2.3:a:redhat:jboss_core_services:-:*:*:*:*:*:*:*
xmlsoft libxml2 < 2.9.4 cpe:2.3:a:xmlsoft:libxml2:*:*:*:*:*:*:*:*

References for CVE-2016-9596

cvelogic Threat Intelligence