Read the docs
TI-2026-76362 Aliases CVE-2026-85312GHSA-r9fc-fx9c-46m4

Saga hijacking in Apache Camel through an unfiltered header

Priority LOW 23CWE-20Published · Updated

Key facts

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

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

Summary

Apache Camel Core from 4.0.0 before 4.18.5 and from 4.19.0 before 4.22.1 is affected. The saga processor trusts a Long-Running-Action header that consumer header filters do not block, which is an improper input validation flaw (CWE-20). A remote sender who can submit inbound messages can supply the header to join a long-running action started by someone else or to have compensation tied to an action they did not start. Exposure is limited to deployments running sagas over an LRA coordinator.

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

Description from the CNA

Improper Input Validation vulnerability in Apache Camel Core component. This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. The saga processor consulted a header named Long-Running-Action to decide which saga an exchange belonged to. The name carries no Camel prefix, so it sits outside the namespace that consumer header filters block, and an external sender could supply it on an inbound message. That let the sender name the saga the exchange joined, attaching their request to a long-running action started by someone else, or causing compensation to be associated with an action they did not initiate. The header is only consulted by a saga service that uses it, which bounds the exposure to deployments running sagas over an LRA coordinator. 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. The header is now consulted only for a saga service that actually uses it, rather than on every exchange. For deployments that cannot upgrade immediately, strip the header at the trust boundary with removeHeaders("Long-Running-Action") on every consumer that accepts messages from an untrusted sender.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00533 45th percentileScored 2026-11-07
Fix Partial Apache Camel (Apache Software Foundation): 4.18.5, 4.22.1, 4.23.0Red Hat: 2 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 to Apache Camel 4.18.5 for the 4.18.x LTS stream, 4.22.1 for the 4.22.x LTS stream, or 4.23.0. The sources list no fixed version for Red Hat Fuse 7 or for Red Hat build of Apache Camel for Spring Boot 4. Until you can upgrade, strip the Long-Running-Action header at the trust boundary on every consumer that accepts messages from untrusted senders.

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
Red Hat build of Apache Camel for Spring Boot 4AffectedNo fix yet: Fix deferred

Timeline

  1. 2026-10-19 Threatist record created from CVE-2026-85312
  2. 2026-10-19 Alias added: GHSA-r9fc-fx9c-46m4
  3. 2026-10-19 CISA SSVC decision points changed
  4. 2026-11-04 Affected versions changed · Red Hat
  5. 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