Is this vulnerability exploitable over the network?

Yes, if an attacker can cause the application or test infrastructure to pass attacker-controlled XML into `isXmlEqualTo(CharSequence)` or `xmlPrettyFormat(String)`. In such cases, exploitation can occur remotely via the same interfaces through which the XML is supplied.

Does exploitation require authentication or local access?

It depends on where and how AssertJ is used. If untrusted XML comes from authenticated users or internal services, an attacker must reach those interfaces. If XML is only taken from local files maintained by developers, the risk is lower. The critical factor is whether an attacker can influence the XML that these methods parse.

What is the safest general fix pattern?

Replace usage of `isXmlEqualTo(CharSequence)` with a hardened XML comparison library that enforces secure parsing (such as XMLUnit), and avoid using `XmlStringPrettyFormatter` with untrusted XML. Centralize XML parsing behind secure helper utilities that disable DTDs and external entities and enable secure processing.

Severity:

CRITICAL RISK

(9.1)

XML External Entity (XXE) Processing (CWE-611) in AssertJ XmlStringPrettyFormatter and isXmlEqualTo

CVE-2026-24400

Published:

Jan 26, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-918

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

Unauthorized Access to Internal Resources via SSRF

May 6, 2026

CWE-863

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Privilege Escalation via Bypassed Access Control

May 6, 2026

Vulnerability Type

Category:

XML External Entity (XXE) Vulnerability

CWE:

CWE-611

Impact:

Information Disclosure, Server-Side Request Forgery (SSRF), and Denial of Service

Severity:

CRITICAL RISK

(9.1)

CVSS Version:

3.1

Vulnerability Type

Category:

XML External Entity (XXE) Vulnerability

CWE:

CWE-611

Impact:

Information Disclosure, Server-Side Request Forgery (SSRF), and Denial of Service

Severity:

CRITICAL RISK

(9.1)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

CodeAnt AI is an offensive and defensive security platform.

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

SOC 2 Type II certified | CodeAnt AI is independently audited and compliant with SOC 2 Type II security standards

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

XML External Entity (XXE) Processing (CWE-611) in AssertJ XmlStringPrettyFormatter and isXmlEqualTo

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Ship clean & secure code faster

Ship clean & secure code faster

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal