Read the docs
TI-2026-76359 Aliases CVE-2026-85296GHSA-ggr9-wchc-h5rx

Cross-partner signing key confusion in Apache Camel AS2 component

Priority LOW 30CWE-488Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
High
Impact type
—
Confidentiality · integrity · availability
High · Low · None
Fix status
Partial Red Hat: 1 without a fix

Attack profile from CVSS 3.1 · CNA. Fix status from CNA and Red Hat.

Summary

Apache Camel from 4.0.0 before 4.18.5 and from 4.19.0 before 4.22.1 stores signing material for one request in state shared across requests. A Message Disposition Notification can therefore be signed with the key of a different trading partner (CWE-488). Ordinary concurrent or successive traffic in multi-partner AS2 deployments reaches this condition, so the attacker needs no special arrangement.

Written with Claude Haiku 5.5 from the sources below · 2026-11-04

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.0068 52nd percentileScored 2026-11-07
Fix Partial Apache Camel (Apache Software Foundation): 4.18.5, 4.22.1, 4.23.0Red Hat: 1 without a fix

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
ApacheApache Camel4.0.0 to before 4.18.5; 4.19.0 to before 4.22.14.18.5, 4.22.1, 4.23.0Patch availableCNA
  • Apache Camel VendorApache Affected 4.0.0 to before 4.18.5; 4.19.0 to before 4.22.1 Fixed in 4.18.5, 4.22.1, 4.23.0 Patch available CNA

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:*4.0.0 to before 4.18.5; 4.19.0 to before 4.22.1VulnerableApache
  • cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:* Versions 4.0.0 to before 4.18.5; 4.19.0 to before 4.22.1 Vulnerable ·Apache

Remediation

Upgrade Apache Camel 4.18.x to 4.18.5, 4.22.x to 4.22.1, or use 4.23.0. Red Hat lists Red Hat Fuse 7 as affected with no fix planned. Until upgrading, run a separate Camel context per trading partner so no signing material is shared between them.

Written with Claude Haiku 5.5 from the sources below · 2026-11-04

  • Fix · CNA Apache Camel (Apache Software Foundation) Fixed in 4.18.5, 4.22.1, 4.23.0

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    Apache Camel 4.18.5, 4.22.1

    39 records Highest priority Priority HIGH 6 HIGH, 9 MEDIUM, 24 LOW

    Other records, highest priority first

    • TI-2026-76322 Unsafe deserialization in Apache Camel camel-hazelcastPriority HIGH 82
    • TI-2026-76339 Path traversal in Apache Camel azure-files componentPriority HIGH 74
    • TI-2026-76330 Path traversal in Apache Camel FTP consumer escapes polled directoryPriority HIGH 74
    Show all 39 records →

Vendor assessments

Red Hat

Red Hat rating: Moderate. Red Hat's page for this CVE →

ProductStatusPlan or fix
Red Hat Fuse 7AffectedNo fix planned: Out of support scope

Timeline

  1. 2026-10-19 Threatist record created from CVE-2026-85296
  2. 2026-10-19 Alias added: GHSA-ggr9-wchc-h5rx
  3. 2026-10-19 CISA SSVC decision points changed
  4. 2026-10-19 Priority changed: MEDIUM → LOW
  5. 2026-11-04 EPSS moved to the 50th–90th percentile
  6. 2026-11-04 Affected versions changed · Red Hat
  7. 2026-11-04 CVSS score added · Red Hat

References

Patch 5

  • TI-2026-76322 Unsafe deserialization in Apache Camel camel-hazelcast CVSS 4.0CRITICAL 10.0
  • TI-2026-18973 Apache Camel: Camel-Keycloak: Cross-Realm Token Acceptance Bypass in KeycloakSecurityPolicy CVSS 3.1CRITICAL 9.1
  • TI-2026-76339 Path traversal in Apache Camel azure-files component CVSS 3.1CRITICAL 9.1
  • TI-2026-76330 Path traversal in Apache Camel FTP consumer escapes polled directory CVSS 3.1CRITICAL 9.1
  • TI-2025-20435 Apache Camel: Camel Message Header Injection via Improper Filtering CVSS 3.1MEDIUM 5.6
  • TI-2026-34899 Apache Camel: Camel-CXF Message Header Injection via Missing Inbound Filtering CVSS 3.1CRITICAL 9.8
See all 116 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences