Live › vulnerability › CVE-2026-85296
Go to dashboardThe Apache Camel AS2 component stored per-request signing material in state shared across requests, so one trading partner's key can be used to sign another partner's Message Disposition Notification. The result is receipts attributed to the wrong partner and cross-partner key confusion, reached through ordinary concurrent multi-partner traffic.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Teams running the Apache Camel AS2 component in Camel 4.0.0 through 4.18.x before 4.18.5, or 4.19.x through 4.22.x before 4.22.1, that serve more than one AS2 trading partner from the same deployment. Single-partner deployments are not described as exposed by the sources, and teams not using camel-as2 can skip it.
No product ranges from the sources yet.
mvn dependency:tree | grep camel-as2 or the camel-as2-* jar version, and confirm whether it falls in 4.0.0 to before 4.18.5 or 4.19.0 to before 4.22.1.4.23.0.4.18.5.4.22.1.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-85296")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.