File disclosure and SSRF via unsafe XML parsing
Published Jan 26, 2026 · Updated Jan 26, 2026
XXE in AssertJ Core 1.4.0 through 3.27.6 allows attackers to read local files, issue server-side requests, or exhaust resources. XmlStringPrettyFormatter.toXmlDocument(String) creates DocumentBuilderFactory with defaults that permit DTDs and external entities. Exploitation requires an application to pass untrusted XML to isXmlEqualTo(CharSequence) or xmlPrettyFormat(String); consequences are file disclosure, SSRF, or a denial-of-service hang.
Summary
What happened
XXE in AssertJ Core 1.4.0 through 3.27.6 allows attackers to read local files, issue server-side requests, or exhaust resources. XmlStringPrettyFormatter.toXmlDocument(String) creates DocumentBuilderFactory with defaults that permit DTDs and external entities. Exploitation requires an application to pass untrusted XML to isXmlEqualTo(CharSequence) or xmlPrettyFormat(String); consequences are file disclosure, SSRF, or a denial-of-service hang.
The record
- CVE
- CVE-2026-24400
- Published
- Jan 26, 2026
- Updated
- Jan 26, 2026
- Vendor
- AssertJ
- Product
- AssertJ Core
- Classifications
- CWE-611
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Jan 26, 2026CVE publishedPublication date reported by the CVE source.
- Jan 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 1.4.0, < 3.27.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo