Skip to content

[Renovate] Update dependency org.assertj:assertj-core to v3 [SECURITY]#410

Open
appsec-renovate-bot[bot] wants to merge 1 commit into
masterfrom
renovate/major-test.assertj
Open

[Renovate] Update dependency org.assertj:assertj-core to v3 [SECURITY]#410
appsec-renovate-bot[bot] wants to merge 1 commit into
masterfrom
renovate/major-test.assertj

Conversation

@appsec-renovate-bot

@appsec-renovate-bot appsec-renovate-bot Bot commented Jun 10, 2026

Copy link
Copy Markdown

This PR contains the following updates:

Package Type Update Change
org.assertj:assertj-core (source) dependencies major 2.9.13.27.7

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


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

CVE-2026-24400 / GHSA-rqfh-9r24-8c9r

More information

Details

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 one of the following methods:

  • isXmlEqualTo(CharSequence) from org.assertj.core.api.AbstractCharSequenceAssert
  • xmlPrettyFormat(String) from org.assertj.core.util.xml.XmlStringPrettyFormatter
Impact

If untrusted XML input is processed by the methods mentioned above (e.g., in test environments handling external fixture files), an attacker could:

  • Read arbitrary local files via file:// URIs (e.g., /etc/passwd, application configuration files)
  • Perform Server-Side Request Forgery (SSRF) via HTTP/HTTPS URIs
  • Cause Denial of Service via "Billion Laughs" entity expansion attacks
Mitigation

isXmlEqualTo(CharSequence) has been deprecated in favor of XMLUnit in version 3.18.0 and will be removed in version 4.0. Users of affected versions should, in order of preference:

  1. Replace isXmlEqualTo(CharSequence) with XMLUnit, or
  2. Upgrade to version 3.27.7, or
  3. Avoid using isXmlEqualTo(CharSequence) or XmlStringPrettyFormatter with untrusted input.

XmlStringPrettyFormatter has historically been considered a utility for isXmlEqualTo(CharSequence) rather than a feature for AssertJ users, so it is deprecated in version 3.27.7 and removed in version 4.0, with no replacement.

References

Severity

  • CVSS Score: 8.2 / 10 (High)
  • Vector String: 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

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate.

@appsec-renovate-bot appsec-renovate-bot Bot changed the title [Renovate] Major update org.assertj:assertj-core to 3.27.7 [Renovate] Major update org.assertj:assertj-core to 3.27.7 (major) Jun 20, 2026
@appsec-renovate-bot appsec-renovate-bot Bot changed the title [Renovate] Major update org.assertj:assertj-core to 3.27.7 (major) [Renovate] Update test.assertj [SECURITY] (major) Jun 23, 2026
@appsec-renovate-bot appsec-renovate-bot Bot changed the title [Renovate] Update test.assertj [SECURITY] (major) [Renovate] Update dependency org.assertj:assertj-core to v3 [SECURITY] Jun 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants