CVE-2026-85296
Description
A flaw was found in the Apache Camel AS2 component. Cryptographic signing material belonging to an individual transaction was stored in a shared state across requests rather than isolated to the active request. Under concurrent network traffic in multi-partner deployments, delivery receipts, known as Message Disposition Notifications (MDNs), can be signed using another partner's cryptographic key. This issue results in cross-partner key confusion and unauthorized information disclosure between trading partners.
Statement
This vulnerability is rated as having a Moderate severity because exploitation requires concurrent multi-tenant exchanges within the same runtime environment and results in information leakage and signature misattribution rather than remote system takeover. In Red Hat integration environments, the AS2 protocol component is utilized for EDI document exchange across business partners. When multiple trading partners are serviced by a single shared Camel routing context, overlapping transactions can inadvertently interchange session signing keys when generating receipt acknowledgments. Deployments that isolate individual partners into separate operational contexts or process transactions sequentially are not exposed to this cross-partner key leakage.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 6.5 | N/A | 6.5 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | High | N/A | High |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | High |
| Integrity Impact | Low | N/A | Low |
| Availability Impact | None | N/A | None |
Vector
Red Hat: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N
cve.org: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Application Data
Data can "bleed" from one session to another through member variables of singleton objects, such as Servlets, and objects from a shared pool. Storing user data in Servlet member fields introduces a data access race condition.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
