---
id: "CVE-2026-85312"
kind: "vulnerability"
aliases: ["CVE-2026-85312"]
title: "Apache Camel: untrusted header lets senders join another saga"
severity: "medium"
cvss: 4.8
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["apache-camel", "integration", "java", "lra", "package", "saga"]
not_affected_if: ["no-saga-usage", "trusted-senders-only", "version-patched"]
published_at: "2026-10-19T11:17:24+00:00"
first_seen_at: "2026-10-23T21:57:18+00:00"
updated_at: "2026-10-25T04:33:33+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-85312", "first_seen_at": "2026-10-23T21:57:18+00:00"}]
---

# Apache Camel: untrusted header lets senders join another saga

Apache Camel's saga processor trusted a header named Long-Running-Action that external senders can set on inbound messages. An attacker can attach their request to a long-running action started by someone else, or trigger compensation for an action they did not start.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the Camel version with `mvn dependency:tree | grep camel-core` or the equivalent in your build tool, and see whether it is below `4.18.5` on the 4.18 line or below `4.22.1` on the 4.22 line
- Search your routes for saga or LRA usage (for example `saga(` or `LRA`) to see whether a saga service consults the header at all

## Fix

- Upgrade Apache Camel to `4.23.0`
- On the 4.18.x LTS stream, upgrade to `4.18.5`
- On the 4.22.x LTS stream, upgrade to `4.22.1`
- Until you can upgrade, call `removeHeaders("Long-Running-Action")` on every consumer that accepts messages from an untrusted sender

## Timeline

- 2026-10-23T21:57:18+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-85312

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_