CVE-2026-24400
XXE in AssertJ enables local file read, SSRF, or DoS via untrusted XML.
Is CVE-2026-24400 being exploited?
Not confirmed. CVE-2026-24400 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.54% probability of exploitation in the next 30 days.
How severe is CVE-2026-24400?
CVE-2026-24400 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-24400?
Yes. A fix has been recorded for CVE-2026-24400. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-24400 affect?
CVE-2026-24400 affects AssertJ, org.assertj.core.util.xml.XmlStringPrettyFormatter, org.assertj.core.api.AbstractCharSequenceAssert. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-24400?
Upgrade to 3.27.7 or avoid affected APIs with untrusted input
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers can read local files via file://, SSRF to internal resources, or cause DoS via entity expansion when untrusted XML is processed.
Patch when possible
- affected>= 1.4.0 and < 3.27.7
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.