It was found that the JAXP implementation used in JBoss EAP 7.0 for SAX and DOM parsing is vulnerable to certain XXE flaws.

published 2018-07-27 8 y ago modified 2026-06-17 4 mo ago also EUVD-2017-16488

cvss: 8.7; version 3.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 1.9%; EPSS 1.9% chance of exploitation in 30 days, percentile 79%
public exploits: 0; none known

It was found that the JAXP implementation used in JBoss EAP 7.0 for SAX and DOM parsing is vulnerable to certain XXE flaws. An attacker could use this flaw to cause DoS, SSRF, or information disclosure if they are able to provide XML content for parsing.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-7464 updated 2026-08-04 cvss 8.7

JBoss: JAXP in EAP 7.0 allows info disclosure via XXE

Red Hat JBoss Enterprise Application Platform 7 XML Frameworks XML Frameworks
affected: workaround, no fix planned “Will not fix”
Red Hat JBoss Enterprise Web Server 3 tomcat Red Hat Mobile Application Platform 4 security
not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.89% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.0	8.7	CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:H
NVD	3.0	9.8	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	7.5	AV:N/AC:L/Au:N/C:P/I:P/A:P

Affected products

[UNKNOWN] JBoss

Classification

Weakness

CWE-611 Improper Restriction of XML External Entity Reference

References

bugzilla.redhat.com /show_bug.cgi?id=CVE-2017-7464
issue-tracking, mitigation, vendor-advisory
securityfocus.com /bid/98450
vdb-entry, third-party-advisory

Sources

CVE List CVE-2017-7464
NVD CVE-2017-7464

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary