Live › vulnerability › CVE-2026-85312
Go to dashboardApache 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 written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Only deployments of Apache Camel 4.0.0 up to but not including 4.18.5, or 4.19.0 up to but not including 4.22.1, that run sagas over an LRA coordinator. The header is read only by a saga service that uses it, so routes without saga or LRA usage are not exposed. Teams that accept inbound messages from untrusted senders are the ones to prioritise.
No product ranges from the sources yet.
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 linesaga( or LRA) to see whether a saga service consults the header at all4.23.04.18.54.22.1removeHeaders("Long-Running-Action") on every consumer that accepts messages from an untrusted senderEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-85312")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.