CVE-2026-85296: Apache Camel: Camel-AS2 Cross-Partner Signing Key Confusion via Shared Per-Request State

Is it exploited?

Not on CISA's list. CISA has not added it to the Known Exploited Vulnerabilities catalog as of 29 Oct 2026. If CISA adds it, this page shows it as known exploited.

How likely is exploitation in the next 30 days?

0.4%

EPSS score, percentile 33.2 of all scored records. A probability estimated by FIRST, not a report of exploitation.

How severe?

6.5 Medium

CVSS v3.1 base score, given by the CNA

What should I do?

Upgrade to Apache Camel 4.23.0, which fixes the issue. Full textSolution from the CVE record.

CISA has set no required action, because the vulnerability is not in KEV.

Advisories and patches (4)

Which versions are affected?

Affected

• from 4.0.0 to before 4.18.5
• from 4.19.0 to before 4.22.1

Unaffected 4.18.5; 4.22.1; 4.23.0

Versions by product

Source: CISA KEV 2026.10.29, as of 29 Oct 2026; FIRST EPSS, as of 29 Oct 2026; CVE List, as of 29 Oct 2026. About the data.

What to do

Solution (from the CVE record)

Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. Per-request signing keys are now confined to the request being processed in ResponseMDN.

Workaround (from the CVE record)

For deployments that cannot upgrade immediately, run a separate Camel context per trading partner so that no signing material is shared between them.

Advisories and patches

• Fix on main, released in 4.23.0 (commit 659176dec58522fbebea11a1f6d5ee5c37f235d9) (Patch)
• Backport to camel-4.22.x, released in 4.22.1 (commit ab5eacd3fa485eb990cf021dc56e48465c060d39) (Patch)
• Backport to camel-4.18.x, released in 4.18.5 (commit 19f91785f9e975e7734efd514946c2dfdbdbd1d7) (Patch)
• Apache Camel Security Advisory - CVE-2026-85296 (Vendor advisory)

This summary is based on the CVE record as of 29 Oct 2026. Check the vendor's advisory before you act: affected versions and fixes can change.

Affected products and versions

As listed in the CVE record.

Versions not listed are: unaffected.

Versions the record lists as unaffected: 4.18.5, 4.22.1, 4.23.0.

Source: CVE List, as of 29 Oct 2026. About the data.

About this vulnerability

Exposure of Data Element to Wrong Session vulnerability in Apache Camel AS2 component. This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. Signing material belonging to an individual request was stored in state that is shared across requests rather than confined to the request being processed. Where a deployment serves more than one trading partner, concurrent…

Summary: CVE record, as of 29 Oct 2026.

• CISA has not added CVE-2026-85296 to its Known Exploited Vulnerabilities (KEV) catalog, as of 29 Oct 2026.
• The CVE record was published on 19 Oct 2026.
• The CVE record carries a CVSS v3.1 base score of 6.5 (Medium), given by its CNA.
• FIRST's EPSS model puts the probability of exploitation in the next 30 days at 0.4% (percentile 33.2), as of 29 Oct 2026. EPSS is a statistical estimate, not a report of exploitation.
• CISA's SSVC assessment in the CVE record: exploitation none, automatable no, technical impact partial.
• The credits in the CVE record name Anthropic (Claude) as finder.

Source: CISA KEV 2026.10.29, as of 29 Oct 2026; CVE List, as of 29 Oct 2026; FIRST EPSS, as of 29 Oct 2026. About the data.

Description

Apache Camel: Camel-AS2 Cross-Partner Signing Key Confusion via Shared Per-Request State

Exposure of Data Element to Wrong Session vulnerability in Apache Camel AS2 component. This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. Signing material belonging to an individual request was stored in state that is shared across requests rather than confined to the request being processed. Where a deployment serves more than one trading partner, concurrent or successive requests could therefore observe each other's material, and a Message Disposition Notification could be signed with the key of a partner other than the one the receipt was for. The result is cross-partner key confusion: a receipt attributable to the wrong partner, and one partner's signing material used while handling another partner's exchange. AS2 deployments are typically multi-partner by design, so the condition is reached by ordinary concurrent traffic rather than by anything the attacker must arrange. Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. Per-request signing keys are now confined to the request being processed in ResponseMDN. For deployments that cannot upgrade immediately, run a separate Camel context per trading partner so that no signing material is shared between them.

Source: CVE List, as of 29 Oct 2026. About the data.

Timeline

Known exploited Apache vulnerabilities

• CVE-2016-3081: Apache Struts Command Injection Vulnerability (added 8 Oct 2026)
• CVE-2026-34486: Apache Tomcat Missing Encryption of Sensitive Data Vulnerability (added 4 Aug 2026)
• CVE-2026-34197: Apache ActiveMQ Improper Input Validation Vulnerability (added 16 Apr 2026)
• CVE-2024-38475: Apache HTTP Server Improper Escaping of Output Vulnerability (added 1 May 2025)
• CVE-2025-24813: Apache Tomcat Path Equivalence Vulnerability (added 1 Apr 2025)