CVE-2026-85312
Last modified
CVE-2026-85312 is a medium-severity vulnerability rated 4.8/10 on the CVSS scale. 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. EPSS estimates a 0.27% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Apache | Camel | >= 4.0.0, < 4.18.5 |
| Apache | Camel | >= 4.19.0, < 4.22.1 |
References
- https://camel.apache.org/security/CVE-2026-85312.htmlMitigation, Patch, Vendor Advisory
- https://github.com/apache/camel/pull/25828Issue Tracking, Patch
- https://github.com/apache/camel/pull/25940Issue Tracking, Patch
- https://github.com/apache/camel/pull/25942Issue Tracking, Patch
- https://issues.apache.org/jira/browse/CAMEL-24449Issue Tracking, Patch, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-85312?
How severe is CVE-2026-85312?
How do I fix CVE-2026-85312?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-85307Insertion of Sensitive Information Into Sent Data vulnerabil…5.3
- CVE-2026-85308Authorization Bypass Through User-Controlled Key vulnerabili…5.3
- CVE-2026-85309Missing Authorization vulnerability in Supsystic Ultimate Ma…5.3
- CVE-2026-8531Heap buffer overflow in WebML in Google Chrome on Windows pr…8.8
- CVE-2026-85310import_contacts Path Traversal in Groundhogg <= 4.7.1 versio…6.5
- CVE-2026-85311Missing Authorization vulnerability in Kings Plugins MarketK…5.3
- CVE-2026-85313Permissive Cross-domain Policy with Untrusted Domains vulner…4.3
- CVE-2026-85314Improper Input Validation vulnerability in Apache Camel Mail…6.5
- CVE-2026-85315Generation of Error Message Containing Sensitive Information…5.3
- CVE-2026-85316Insufficient Granularity of Access Control vulnerability in …4.8
- CVE-2026-85317Use of Cache Containing Sensitive Information vulnerability …4.8
- CVE-2026-85318Heap-based buffer overflow in Servicing Stack Updates allows…7.8
Are you affected by CVE-2026-85312?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
