{"id":"CVE-2026-85296","title":"Apache Camel: Camel-AS2 Cross-Partner Signing Key Confusion via Shared Per-Request State","summary":"Exposure of Data Element to Wrong Session vulnerability in Apache Camel AS2 component.\n\nThis issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.\n\nSigning material belonging to an individual request was stored…","severity":"medium","cvss":6.5,"cvssVector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N","cvssSource":"cna","cwe":["CWE-488"],"vendor":"Apache Software Foundation","product":"org.apache.camel:camel-as2","affected":["org.apache.camel:camel-as2 >= 4.0.0 < 4.18.5","org.apache.camel:camel-as2 >= 4.19.0 < 4.22.1"],"published":"2026-10-19","updated":"2026-10-19","sourceUpdated":"2026-10-19T10:38:11.146Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-85296","references":[{"url":"https://camel.apache.org/security/CVE-2026-85296.html","label":"Apache Camel Security Advisory - CVE-2026-85296"},{"url":"https://issues.apache.org/jira/browse/CAMEL-24429","label":"CAMEL-24429"},{"url":"https://github.com/apache/camel/pull/25641","label":"Fix on main, released in 4.23.0 (commit 659176dec58522fbebea11a1f6d5ee5c37f235d9)"},{"url":"https://github.com/apache/camel/pull/25869","label":"Backport to camel-4.22.x, released in 4.22.1 (commit ab5eacd3fa485eb990cf021dc56e48465c060d39)"},{"url":"https://github.com/apache/camel/pull/25870","label":"Backport to camel-4.18.x, released in 4.18.5 (commit 19f91785f9e975e7734efd514946c2dfdbdbd1d7)"}],"tags":["cve.org"],"ingestedAt":"2026-10-19T12:27:23.811Z","slug":"CVE-2026-85296","body":"## Overview\n\nExposure of Data Element to Wrong Session vulnerability in Apache Camel AS2 component.\n\nThis issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.\n\nSigning 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.\n\nUpgrade 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.\n\n## Affected\n\n- `org.apache.camel:camel-as2 >= 4.0.0 < 4.18.5`\n- `org.apache.camel:camel-as2 >= 4.19.0 < 4.22.1`\n\n## Remediation\n\nUpgrade 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.\n\n### Workarounds\n\nFor deployments that cannot upgrade immediately, run a separate Camel context per trading partner so that no signing material is shared between them.","depth":"sunlit","depthScore":36,"depthScoreParts":{"impact":35.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}