Medium 6.5Published Oct 19, 2026

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

Updated under an hour ago (2026-10-19 11:40 UTC)

Does this affect you?

It affects Apache Software Foundation Apache Camel. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for Apache Software Foundation Apache Camel

Exploited in the last 30 days

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.

CVSS: 6.5 MEDIUM (v3.1, CNA)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N
Weakness (CWE): CWE-488
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: apache
NVD analysis: Received
Record last updated: Oct 19, 2026
First seen by InfoSec Signals: Oct 19, 2026

Affected products

Affected products

Apache Software Foundation Apache Camel apache_software_foundation:apache_camel (from the name)	from 4.0.0 before 4.18.5; from 4.19.0 before 4.22.1; 4.18.5 not affected; 4.22.1 not affected; 4.23.0 not affected	CNA record

References

https://camel.apache.org/security/CVE-2026-85296.htmlvendor-advisory
https://issues.apache.org/jira/browse/CAMEL-24429issue-tracking
https://github.com/apache/camel/pull/25641patch
https://github.com/apache/camel/pull/25869patch
https://github.com/apache/camel/pull/25870patch

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.