Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-rqfh-9r24-8c9r

AssertJ has XML External Entity (XXE) vulnerability when parsing untrusted XML via isXmlEqualTo assertion

CVSS 8.2 HighEPSS 0.0057 · 47th percentile

Published by the GitHub Advisory Database at 26 Jan 2026, 21:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.assertj:assertj-coreMaven>=1.4.0, <3.27.73.27.7
Identifiers
GHSA-rqfh-9r24-8c9r · CVE-2026-24400
Weakness (CWE)
CWE-611
Tags
Published
26 Jan 2026
Updated
3 Feb 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

AssertJ (org.assertj:assertj-core) versions 1.4.0 up to 3.27.7 are affected by an XML External Entity vulnerability in the isXmlEqualTo(CharSequence) assertion and XmlStringPrettyFormatter, which parse XML with default settings that allow external entities. An attacker who can supply untrusted XML to these methods could read local files, perform server-side request forgery, or cause denial of service through entity expansion. Upgrade to version 3.27.7, or replace isXmlEqualTo with XMLUnit, and avoid passing untrusted XML to these methods.

Written 7 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.2 High 4.0 CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:L/SC:H/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0057, the 47th percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:09 UTC First seen by agentprime
  2. 31 Oct 2026, 15:09 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.