CVE intelligence and bounded remediation

CVE-2026-24400 — AssertJ provides Fluent testing assertions for Java and the Java Virtual Machine (JVM)

Critical CVSS 9.1

AssertJ provides Fluent testing assertions for Java and the Java Virtual Machine (JVM). Starting in version 1.4.0 and prior to version 3.27.7, an XML External Entity (XXE) vulnerability exists in `org.assertj.core.util.xml.XmlStringPrettyFormatter`: the `toXmlDocument(String)` method initializes `DocumentBuilderFactory` with default settings, without disabling DTDs or external entities. This formatter is used by the `isXmlEqualTo(CharSequence)` assertion for `CharSequence` values. An application is vulnerable only when it uses untrusted XML input with either `isXmlEqualTo(CharSequence)` from `org.assertj.core.api.AbstractCharSequenceAssert` or `xmlPrettyFormat(String)` from `org.assertj.core.util.xml.XmlStringPrettyFormatter`. If untrusted XML input is processed by tone of these methods, an attacker couldnread arbitrary local files via `file://` URIs (e.g., `/etc/passwd`, application configuration files); perform Server-Side Request Forgery (SSRF) via HTTP/HTTPS URIs, and/or cause Denial of Service via "Billion Laughs" entity expansion attacks. `isXmlEqualTo(CharSequence)` has been deprecated in favor of XMLUnit in version 3.18.0 and will be removed in version 4.0. Users of affect…

Severity
Critical
CVSS
9.1 (3.1)
Published
2026-01-26
CISA KEV
Not currently listed
Ecosystem
java/maven
Weaknesses
CWE-611

Affected products

  • assertj / assertj

Matched remediation archetype

XML external entity and unsafe XML processing

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Inventory XML parsers used by APIs, file imports, office or image formats, identity protocols, feeds, and background jobs.
  • Determine whether document type declarations, external entities, XInclude, schemas, or network resolvers are enabled.
  • Map parser filesystem and network access and the sensitivity of documents it processes.

Remediate safely

  • Configure each parser to reject document type declarations and disable external entity, XInclude, and network resolution features.
  • Prefer a data format or hardened parser that does not support external resolution, and apply input size and depth limits.
  • Update affected XML libraries and centralize secure parser construction so callers cannot silently override it.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.