---
id: CVE-2026-85312
title: >-
  Apache Camel: Camel-Core Saga Participation Hijacking via the Unfiltered
  Long-Running-Action Header
summary: >-
  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 whi…
severity: medium
cvss: 4.8
cvssVector: 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N'
cvssSource: cna
cwe:
  - CWE-20
vendor: Apache Software Foundation
product: 'org.apache.camel:camel-core'
affected:
  - 'org.apache.camel:camel-core >= 4.0.0 < 4.18.5'
  - 'org.apache.camel:camel-core >= 4.19.0 < 4.22.1'
published: '2026-10-19'
updated: '2026-10-19'
sourceUpdated: '2026-10-19T10:40:30.029Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2026-85312'
references:
  - url: 'https://camel.apache.org/security/CVE-2026-85312.html'
    label: Apache Camel Security Advisory - CVE-2026-85312
  - url: 'https://issues.apache.org/jira/browse/CAMEL-24449'
    label: CAMEL-24449
  - url: 'https://github.com/apache/camel/pull/25828'
    label: >-
      Fix on main, released in 4.23.0 (commit
      dfde003151a0753f997f9eea7d071097f4b00db2)
  - url: 'https://github.com/apache/camel/pull/25940'
    label: >-
      Backport to camel-4.22.x, released in 4.22.1 (commit
      260989268cbc6d258b1fcba63770be8ebbec40cb)
  - url: 'https://github.com/apache/camel/pull/25942'
    label: >-
      Backport to camel-4.18.x, released in 4.18.5 (commit
      af1efbcccf5882b1ef0094db718972da3190e7e9)
tags:
  - cve.org
ingestedAt: '2026-10-19T12:27:23.810Z'
---

## Overview

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.

## Affected

- `org.apache.camel:camel-core >= 4.0.0 < 4.18.5`
- `org.apache.camel:camel-core >= 4.19.0 < 4.22.1`

## Remediation

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.

### Workarounds

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.