BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-24400High confidence

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

assertj · assertj

Official source article: GitHub GHSA-RQFH-9R24-8C9R ↗. Check the applicable product and release in the original source.

8.2HighCVSS 4.0
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 4 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 27 Jan 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.58% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs assertj assertj and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 4 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 4 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourceassertj-coreAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourceassertj-coreAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourceassertj-coreAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourceassertj-coreAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archiveassertj-coreUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Open-source package ranges1 source-attributed range

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
mavenorg.assertj:assertj-core>= 1.4.0, <= 3.27.63.27.7GitHub advisory ↗upstream repository advisory · 29 Jan 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-24400 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityassertj: AssertJ: Information disclosure and denial of service via XML External Entity (XXE)
16 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • openshift-serverless-1/kn-ekb-dispatcher-rhel9 as a component of OpenShift Serverless
  • openshift-serverless-1/kn-ekb-receiver-rhel9 as a component of OpenShift Serverless
  • assertj-core as a component of Red Hat build of Apache Camel - HawtIO 4
  • assertj-core as a component of Red Hat build of Debezium 2
  • assertj-core as a component of Red Hat build of Debezium 3
  • assertj-core as a component of Red Hat build of OptaPlanner 8
  • assertj-core-javadoc (javapackages-tools:201801) as a component of Red Hat Enterprise Linux 8
  • assertj-core.src (javapackages-tools:201801) as a component of Red Hat Enterprise Linux 8
  • assertj-core (javapackages-tools:201801) as a component of Red Hat Enterprise Linux 8
  • log4j-jcl as a component of Red Hat Enterprise Linux 9
  • log4j-slf4j as a component of Red Hat Enterprise Linux 9
  • log4j.src as a component of Red Hat Enterprise Linux 9
Summary
A flaw was found in AssertJ. An XML External Entity (XXE) vulnerability exists in the `XmlStringPrettyFormatter` component, which is used by the `isXmlEqualTo(CharSequence)` assertion. If an application processes untrusted XML input using these methods, a remote attacker could exploit this flaw to read arbitrary local files, perform Server-Side Request Forgery (SSRF) by making the server request arbitrary URLs, or cause a Denial of Service (DoS) through entity expansion attacks.
Remediation
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-4724

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 4 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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 affected versions should, in order of preference: replace `isXmlEqualTo(CharSequence)` with XMLUnit, upgrade to version 3.27.7, or 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.

What

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 affected versions should, in order of preference: replace `isXmlEqualTo(CharSequence)` with XMLUnit, upgrade to version 3.27.7, or 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.

Why

The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may obtain information outside the intended access boundary.

What

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 affected versions should, in order of preference: replace `isXmlEqualTo(CharSequence)` with XMLUnit, upgrade to version 3.27.7, or 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.

Why

The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may obtain information outside the intended access boundary.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Improper Restriction of XML External Entity Reference → obtain information outside the intended access boundary
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Not a CVSS 4.0 base metric
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-611 ↗

CWE-611: Improper Restriction of XML External Entity Reference. The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
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

Common Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATNoneAttack requirements: No additional deployment or execution condition is required.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.VCHighVulnerable-system confidentiality: A successful attack can cause a major loss.VINoneVulnerable-system integrity: No direct loss is represented by this metric.VALowVulnerable-system availability: A successful attack can cause a limited loss.SCHighSubsequent-system confidentiality: A successful attack can cause a major loss.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
Denial of serviceCWE-611
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-2451Oracle Siebel CRM: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Siebel CRM ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2026-2437Oracle Communications: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Communications ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2026-0851IBM InfoSphere Information Server: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in IBM InfoSphere Information Server ausnutzen, um Sicherheitsmaßnahmen zu umgehen, einen Denial of Service zu verursachen, einen Cross Site Scripting und CSRF Angriff durchzuführen, Informationen offenzulegen und Daten zu manipulieren.

Official advisory ↗
BSI · German · WID-SEC-2026-2972Red Hat Enterprise Linux (assertj): Schwachstelle ermöglicht Offenlegung von Informationen und DoS

Ein lokaler Angreifer kann eine Schwachstelle in Red Hat Enterprise Linux (assertj) ausnutzen, um Informationen offenzulegen, und um einen Denial of Service Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260128Security Bulletin 28 Jan 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 28 Jan 2026, published on 28 January 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-006706AssertJにおけるXML 外部エンティティの脆弱性

AssertJはJavaおよびJava仮想マシン（JVM）向けのFluentテストアサーションを提供するツールです。バージョン1.4.0から3.27.7未満の間、`org.assertj.core.util.xml.XmlStringPrettyFormatter`にXML外部エンティティ（XXE）脆弱性が存在していました。具体的には、`toXmlDocument(String)`メソッドが`DocumentBuilderFactory`をデフォルト設定で初期化しており、DTDや外部エンティティを無効化していなかったためです。このフォーマッターは、`CharSequence`値に対する`isXmlEqualTo(CharSequence)`アサーションで使用されています。アプリケーションが信頼されていないXML入力を`org.assertj.core.api.AbstractCharSequenceAssert`の`isXmlEqualTo(CharSequence)`または`org.assertj.core.util.xml.XmlStringPrettyFormatter`の`xmlPrettyFormat(String)`で処理すると脆弱性が生じます。これらのメソッドで信頼されていないXML入力を処理する場合、攻撃者は`file://`URI（例：`/etc/passwd`やアプリケーション設定ファイル）を介して任意のローカルファイルを読み取ったり、HTTP/HTTPS URIを利用したサーバーサイドリクエストフォージェリ（SSRF）を行ったり、「ビリオンラフ」エンティティ展開攻撃によるサービス拒否（DoS）を引き起こす可能性があります。`isXmlEqualTo(CharSequence)`はバージョン3.18.0でXMLUnitに置き換えられ非推奨となり、バージョン4.0で削除される予定です。影響を受けるバージョンのユーザーには、優先的に`isXmlEqualTo(CharSequence)`をXMLUnitに置き換えること、バージョン3.27.7にアップグレードすること、または信頼されていない入力に対して`isXmlEqualTo(CharSequence)`や`XmlStringPrettyFormatter`を使用しないことを推奨します。`XmlStringPrettyFormatter`はこれまで`isXmlEqualTo(CharSequence)`のユーティリティとして扱われており、バージョン3.27.7で非推奨となり、4.0で削除されますが代替手段はありません。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
A mitigation or workaround reference is available from the source linked below; validate it against the affected product and version.
04

Evidence and provenance

Published 26 Jan 2026 · Last source change 27 Jan 2026, 21:36 UTC · CWE-611 · Improper Restriction of XML External Entity Reference

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-4724
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    >= 1.4.0, < 3.27.7 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
    After
    >= 1.4.0, < 3.27.7 · Fixed: Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
    Red Hat Product Security ↗
  2. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-24400 to remediation: access.redhat.com/CVE-2026-24400.
    Before
    remediation: access.redhat.com/CVE-2026-24400
    After
    remediation: access.redhat.com/CVE-2026-24400
    Red Hat Product Security ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    openshift-serverless-1/kn-ekb-dispatcher-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-ekb-receiver-rhel9 as a component of OpenShift Serverless; assertj-core as a component of Red Hat AMQ Clients; assertj-core as a component of Red Hat build of Apache Camel - HawtIO 4; assertj-core as a component of Red Hat build of Debezium 2; assertj-core as a component of Red Hat build of Debezium 3; assertj-core as a component of Red Hat build of OptaPlanner 8; assertj-core-javadoc (javapackages-tools:201801) as a component of Red Hat Enterprise Linux 8; assertj-core.src (javapackages-tools:201801) as a component of Red Hat Enterprise Linux 8; assertj-core (javapackages-tools:201801) as a component of Red Hat Enterprise Linux 8; log4j-jcl as a component of Red Hat Enterprise Linux 9; log4j-slf4j as a component of Red Hat Enterprise Linux 9; log4j.src as a component of Red Hat Enterprise Linux 9; assertj-core as a component of Red Hat Fuse 7; assertj-core as a component of Red Hat JBoss Enterprise Application Platform 8; assertj-core as a component of Red Hat Process Automation 7; assertj-core as a component of streams for Apache Kafka 3 · Fixed: assertj-core-0:3.24.2-9.el10_2.1.noarch as a component of Red Hat Enterprise Linux AppStream (v. 10); assertj-core-0:3.24.2-9.el10_2.1.src as a component of Red Hat Enterprise Linux AppStream (v. 10); assertj-core-0:3.19.0-5.el9_2.2.noarch as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2); assertj-core-0:3.19.0-5.el9_2.2.src as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2); assertj-core-0:3.19.0-5.el9_4.2.noarch as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4); assertj-core-0:3.19.0-5.el9_4.2.src as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4); assertj-core-0:3.19.0-9.el9_6.1.noarch as a component of Red Hat Enterprise Linux AppStream EUS (v.9.6); assertj-core-0:3.19.0-9.el9_6.1.src as a component of Red Hat Enterprise Linux AppStream EUS (v.9.6); assertj-core-0:3.19.0-9.el9_8.1.noarch as a component of Red Hat Enterprise Linux AppStream (v. 9); assertj-core-0:3.19.0-9.el9_8.1.src as a component of Red Hat Enterprise Linux AppStream (v. 9); assertj-core-javadoc-0:3.24.2-9.el10_2.1.noarch as a component of Red Hat Enterprise Linux CodeReady Linux Builder (v. 10); Red Hat build of Apache Camel 4.18.1.P1 for Spring Boot 3.5.16
    After
    openshift-serverless-1/kn-ekb-dispatcher-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-ekb-receiver-rhel9 as a component of OpenShift Serverless; assertj-core as a component of Red Hat build of Apache Camel - HawtIO 4; assertj-core as a component of Red Hat build of Debezium 2; assertj-core as a component of Red Hat build of Debezium 3; assertj-core as a component of Red Hat build of OptaPlanner 8; assertj-core-javadoc (javapackages-tools:201801) as a component of Red Hat Enterprise Linux 8; assertj-core.src (javapackages-tools:201801) as a component of Red Hat Enterprise Linux 8; assertj-core (javapackages-tools:201801) as a component of Red Hat Enterprise Linux 8; log4j-jcl as a component of Red Hat Enterprise Linux 9; log4j-slf4j as a component of Red Hat Enterprise Linux 9; log4j.src as a component of Red Hat Enterprise Linux 9; assertj-core as a component of Red Hat Fuse 7; assertj-core as a component of Red Hat JBoss Enterprise Application Platform 8; assertj-core as a component of Red Hat Process Automation 7; assertj-core as a component of streams for Apache Kafka 3 · Fixed: AMQ Clients 2026.Q3; assertj-core-0:3.24.2-9.el10_0.1.noarch as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); assertj-core-0:3.24.2-9.el10_0.1.src as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); assertj-core-0:3.24.2-9.el10_2.1.noarch as a component of Red Hat Enterprise Linux AppStream (v. 10); assertj-core-0:3.24.2-9.el10_2.1.src as a component of Red Hat Enterprise Linux AppStream (v. 10); assertj-core-0:3.19.0-5.el9_2.2.noarch as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2); assertj-core-0:3.19.0-5.el9_2.2.src as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2); assertj-core-0:3.19.0-5.el9_4.2.noarch as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4); assertj-core-0:3.19.0-5.el9_4.2.src as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4); assertj-core-0:3.19.0-9.el9_6.1.noarch as a component of Red Hat Enterprise Linux AppStream EUS (v.9.6); assertj-core-0:3.19.0-9.el9_6.1.src as a component of Red Hat Enterprise Linux AppStream EUS (v.9.6); assertj-core-0:3.19.0-9.el9_8.1.noarch as a component of Red Hat Enterprise Linux AppStream (v. 9); assertj-core-0:3.19.0-9.el9_8.1.src as a component of Red Hat Enterprise Linux AppStream (v. 9); assertj-core-javadoc-0:3.24.2-9.el10_0.1.noarch as a component of Red Hat Enterprise Linux CodeReady Linux Builder EUS (v. 10.0); assertj-core-javadoc-0:3.24.2-9.el10_2.1.noarch as a component of Red Hat Enterprise Linux CodeReady Linux Builder (v. 10); Red Hat build of Apache Camel 4.18.1.P1 for Spring Boot 3.5.16
    Red Hat Product Security ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    >= 1.4.0, < 3.27.7 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    After
    >= 1.4.0, < 3.27.7 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
    Red Hat Product Security ↗
  5. Affected versionsThe structured affected or fixed version information changed.
    Before
    openshift-serverless-1/kn-ekb-dispatcher-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-ekb-receiver-rhel9 as a component of OpenShift Serverless; assertj-core as a component of Red Hat AMQ Clients; assertj-core as a component of Red Hat build of Apache Camel - HawtIO 4; assertj-core as a component of Red Hat build of Debezium 2; assertj-core as a component of Red Hat build of Debezium 3; assertj-core as a component of Red Hat build of OptaPlanner 8; assertj-core-javadoc (javapackages-tools:201801) as a component of Red Hat Enterprise Linux 8; assertj-core.src (javapackages-tools:201801) as a component of Red Hat Enterprise Linux 8; assertj-core (javapackages-tools:201801) as a component of Red Hat Enterprise Linux 8; assertj-core.src as a component of Red Hat Enterprise Linux 9; log4j-jcl as a component of Red Hat Enterprise Linux 9; log4j-slf4j as a component of Red Hat Enterprise Linux 9; log4j.src as a component of Red Hat Enterprise Linux 9; assertj-core as a component of Red Hat Fuse 7; assertj-core as a component of Red Hat JBoss Enterprise Application Platform 8; devspaces/devspaces-operator-bundle as a component of Red Hat OpenShift Dev Spaces; assertj-core as a component of Red Hat Process Automation 7; assertj-core as a component of streams for Apache Kafka 3 · Fixed: assertj-core-0:3.24.2-9.el10_2.1.noarch as a component of Red Hat Enterprise Linux AppStream (v. 10); assertj-core-0:3.24.2-9.el10_2.1.src as a component of Red Hat Enterprise Linux AppStream (v. 10); assertj-core-0:3.19.0-5.el9_2.2.noarch as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2); assertj-core-0:3.19.0-5.el9_2.2.src as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2); assertj-core-0:3.19.0-5.el9_4.2.noarch as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4); assertj-core-0:3.19.0-5.el9_4.2.src as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4); assertj-core-0:3.19.0-9.el9_6.1.noarch as a component of Red Hat Enterprise Linux AppStream EUS (v.9.6); assertj-core-0:3.19.0-9.el9_6.1.src as a component of Red Hat Enterprise Linux AppStream EUS (v.9.6); assertj-core-javadoc-0:3.24.2-9.el10_2.1.noarch as a component of Red Hat Enterprise Linux CodeReady Linux Builder (v. 10); Red Hat build of Apache Camel 4.18.1.P1 for Spring Boot 3.5.16
    After
    openshift-serverless-1/kn-ekb-dispatcher-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-ekb-receiver-rhel9 as a component of OpenShift Serverless; assertj-core as a component of Red Hat AMQ Clients; assertj-core as a component of Red Hat build of Apache Camel - HawtIO 4; assertj-core as a component of Red Hat build of Debezium 2; assertj-core as a component of Red Hat build of Debezium 3; assertj-core as a component of Red Hat build of OptaPlanner 8; assertj-core-javadoc (javapackages-tools:201801) as a component of Red Hat Enterprise Linux 8; assertj-core.src (javapackages-tools:201801) as a component of Red Hat Enterprise Linux 8; assertj-core (javapackages-tools:201801) as a component of Red Hat Enterprise Linux 8; log4j-jcl as a component of Red Hat Enterprise Linux 9; log4j-slf4j as a component of Red Hat Enterprise Linux 9; log4j.src as a component of Red Hat Enterprise Linux 9; assertj-core as a component of Red Hat Fuse 7; assertj-core as a component of Red Hat JBoss Enterprise Application Platform 8; assertj-core as a component of Red Hat Process Automation 7; assertj-core as a component of streams for Apache Kafka 3 · Fixed: assertj-core-0:3.24.2-9.el10_2.1.noarch as a component of Red Hat Enterprise Linux AppStream (v. 10); assertj-core-0:3.24.2-9.el10_2.1.src as a component of Red Hat Enterprise Linux AppStream (v. 10); assertj-core-0:3.19.0-5.el9_2.2.noarch as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2); assertj-core-0:3.19.0-5.el9_2.2.src as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2); assertj-core-0:3.19.0-5.el9_4.2.noarch as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4); assertj-core-0:3.19.0-5.el9_4.2.src as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4); assertj-core-0:3.19.0-9.el9_6.1.noarch as a component of Red Hat Enterprise Linux AppStream EUS (v.9.6); assertj-core-0:3.19.0-9.el9_6.1.src as a component of Red Hat Enterprise Linux AppStream EUS (v.9.6); assertj-core-0:3.19.0-9.el9_8.1.noarch as a component of Red Hat Enterprise Linux AppStream (v. 9); assertj-core-0:3.19.0-9.el9_8.1.src as a component of Red Hat Enterprise Linux AppStream (v. 9); assertj-core-javadoc-0:3.24.2-9.el10_2.1.noarch as a component of Red Hat Enterprise Linux CodeReady Linux Builder (v. 10); Red Hat build of Apache Camel 4.18.1.P1 for Spring Boot 3.5.16
    Red Hat Product Security ↗
  6. Affected versionsThe structured affected or fixed version information changed.
    Before
    openshift-serverless-1/kn-ekb-dispatcher-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-ekb-receiver-rhel9 as a component of OpenShift Serverless; assertj-core as a component of Red Hat AMQ Clients; assertj-core as a component of Red Hat build of Apache Camel - HawtIO 4; assertj-core as a component of Red Hat build of Debezium 2; assertj-core as a component of Red Hat build of Debezium 3; assertj-core as a component of Red Hat build of OptaPlanner 8; assertj-core-javadoc as a component of Red Hat Enterprise Linux 10; assertj-core.src as a component of Red Hat Enterprise Linux 10; assertj-core-javadoc (javapackages-tools:201801) as a component of Red Hat Enterprise Linux 8; assertj-core.src (javapackages-tools:201801) as a component of Red Hat Enterprise Linux 8; assertj-core (javapackages-tools:201801) as a component of Red Hat Enterprise Linux 8; assertj-core.src as a component of Red Hat Enterprise Linux 9; log4j-jcl as a component of Red Hat Enterprise Linux 9; log4j-slf4j as a component of Red Hat Enterprise Linux 9; log4j.src as a component of Red Hat Enterprise Linux 9; assertj-core as a component of Red Hat Fuse 7; assertj-core as a component of Red Hat JBoss Enterprise Application Platform 8; devspaces/devspaces-operator-bundle as a component of Red Hat OpenShift Dev Spaces; assertj-core as a component of Red Hat Process Automation 7; assertj-core as a component of streams for Apache Kafka 3 · Fixed: assertj-core-0:3.19.0-5.el9_2.2.noarch as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2); assertj-core-0:3.19.0-5.el9_2.2.src as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2); Red Hat build of Apache Camel 4.18.1.P1 for Spring Boot 3.5.16
    After
    openshift-serverless-1/kn-ekb-dispatcher-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-ekb-receiver-rhel9 as a component of OpenShift Serverless; assertj-core as a component of Red Hat AMQ Clients; assertj-core as a component of Red Hat build of Apache Camel - HawtIO 4; assertj-core as a component of Red Hat build of Debezium 2; assertj-core as a component of Red Hat build of Debezium 3; assertj-core as a component of Red Hat build of OptaPlanner 8; assertj-core-javadoc (javapackages-tools:201801) as a component of Red Hat Enterprise Linux 8; assertj-core.src (javapackages-tools:201801) as a component of Red Hat Enterprise Linux 8; assertj-core (javapackages-tools:201801) as a component of Red Hat Enterprise Linux 8; assertj-core.src as a component of Red Hat Enterprise Linux 9; log4j-jcl as a component of Red Hat Enterprise Linux 9; log4j-slf4j as a component of Red Hat Enterprise Linux 9; log4j.src as a component of Red Hat Enterprise Linux 9; assertj-core as a component of Red Hat Fuse 7; assertj-core as a component of Red Hat JBoss Enterprise Application Platform 8; devspaces/devspaces-operator-bundle as a component of Red Hat OpenShift Dev Spaces; assertj-core as a component of Red Hat Process Automation 7; assertj-core as a component of streams for Apache Kafka 3 · Fixed: assertj-core-0:3.24.2-9.el10_2.1.noarch as a component of Red Hat Enterprise Linux AppStream (v. 10); assertj-core-0:3.24.2-9.el10_2.1.src as a component of Red Hat Enterprise Linux AppStream (v. 10); assertj-core-0:3.19.0-5.el9_2.2.noarch as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2); assertj-core-0:3.19.0-5.el9_2.2.src as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2); assertj-core-0:3.19.0-5.el9_4.2.noarch as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4); assertj-core-0:3.19.0-5.el9_4.2.src as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4); assertj-core-0:3.19.0-9.el9_6.1.noarch as a component of Red Hat Enterprise Linux AppStream EUS (v.9.6); assertj-core-0:3.19.0-9.el9_6.1.src as a component of Red Hat Enterprise Linux AppStream EUS (v.9.6); assertj-core-javadoc-0:3.24.2-9.el10_2.1.noarch as a component of Red Hat Enterprise Linux CodeReady Linux Builder (v. 10); Red Hat build of Apache Camel 4.18.1.P1 for Spring Boot 3.5.16
    Red Hat Product Security ↗
  7. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-24400 to remediation: access.redhat.com/CVE-2026-24400.
    Before
    remediation: access.redhat.com/CVE-2026-24400
    After
    remediation: access.redhat.com/CVE-2026-24400
    Red Hat Product Security ↗
  8. Affected versionsThe structured affected or fixed version information changed.
    Before
    openshift-serverless-1/kn-ekb-dispatcher-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-ekb-receiver-rhel9 as a component of OpenShift Serverless; assertj-core as a component of Red Hat AMQ Clients; assertj-core as a component of Red Hat build of Apache Camel - HawtIO 4; assertj-core as a component of Red Hat build of Debezium 2; assertj-core as a component of Red Hat build of Debezium 3; assertj-core as a component of Red Hat build of OptaPlanner 8; assertj-core-javadoc as a component of Red Hat Enterprise Linux 10; assertj-core.src as a component of Red Hat Enterprise Linux 10; assertj-core-javadoc (javapackages-tools:201801) as a component of Red Hat Enterprise Linux 8; assertj-core.src (javapackages-tools:201801) as a component of Red Hat Enterprise Linux 8; assertj-core (javapackages-tools:201801) as a component of Red Hat Enterprise Linux 8; assertj-core.src as a component of Red Hat Enterprise Linux 9; log4j-jcl as a component of Red Hat Enterprise Linux 9; log4j-slf4j as a component of Red Hat Enterprise Linux 9; log4j.src as a component of Red Hat Enterprise Linux 9; assertj-core as a component of Red Hat Fuse 7; assertj-core as a component of Red Hat JBoss Enterprise Application Platform 8; devspaces/devspaces-operator-bundle as a component of Red Hat OpenShift Dev Spaces; assertj-core as a component of Red Hat Process Automation 7; assertj-core as a component of streams for Apache Kafka 3 · Fixed: Red Hat build of Apache Camel 4.18.1.P1 for Spring Boot 3.5.16
    After
    openshift-serverless-1/kn-ekb-dispatcher-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-ekb-receiver-rhel9 as a component of OpenShift Serverless; assertj-core as a component of Red Hat AMQ Clients; assertj-core as a component of Red Hat build of Apache Camel - HawtIO 4; assertj-core as a component of Red Hat build of Debezium 2; assertj-core as a component of Red Hat build of Debezium 3; assertj-core as a component of Red Hat build of OptaPlanner 8; assertj-core-javadoc as a component of Red Hat Enterprise Linux 10; assertj-core.src as a component of Red Hat Enterprise Linux 10; assertj-core-javadoc (javapackages-tools:201801) as a component of Red Hat Enterprise Linux 8; assertj-core.src (javapackages-tools:201801) as a component of Red Hat Enterprise Linux 8; assertj-core (javapackages-tools:201801) as a component of Red Hat Enterprise Linux 8; assertj-core.src as a component of Red Hat Enterprise Linux 9; log4j-jcl as a component of Red Hat Enterprise Linux 9; log4j-slf4j as a component of Red Hat Enterprise Linux 9; log4j.src as a component of Red Hat Enterprise Linux 9; assertj-core as a component of Red Hat Fuse 7; assertj-core as a component of Red Hat JBoss Enterprise Application Platform 8; devspaces/devspaces-operator-bundle as a component of Red Hat OpenShift Dev Spaces; assertj-core as a component of Red Hat Process Automation 7; assertj-core as a component of streams for Apache Kafka 3 · Fixed: assertj-core-0:3.19.0-5.el9_2.2.noarch as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2); assertj-core-0:3.19.0-5.el9_2.2.src as a component of Red Hat Enterprise Linux AppStream E4S (v.9.2); Red Hat build of Apache Camel 4.18.1.P1 for Spring Boot 3.5.16
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
Fixed release recorded from official guidance
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2026-4724↗Red Hat Product Security security advisory↗CVE authority or vendor reference · GitHub GHSA-RQFH-9R24-8C9R↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-24400 · cve.blacktree.nl