{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-85312 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-85312 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-85312 is a medium-severity missing authorization vulnerability in Apache Camel, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-85312 and fix it if it is affected.\n\nWhat it is: CVE-2026-85312 is a medium-severity missing authorization vulnerability in Apache Camel, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-85312 in the wild and no public exploit code.\n\nAffected product: Apache Camel. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-85312/ (Markdown: https://insights.sbomify.com/CVE-2026-85312/index.md)","id":"CVE-2026-85312","markdown":"https://insights.sbomify.com/CVE-2026-85312/index.md","name":"CVE-2026-85312","record":{"aliases":["GHSA-r9fc-fx9c-46m4"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Apache Camel integration framework","requires_auth":"none","summary":"Attackers can hijack saga transactions by injecting an unfiltered header, requiring deployments using LRA coordinators to upgrade or strip the header.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Improper Input Validation vulnerability in Apache Camel Core component.\n\nThis issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.\n\nThe 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.\n\nUpgrade 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-10-20","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-10-20T12:26:29Z","kind":"github_poc","ref":"https://github.com/oscerd/CVE-2026-85312","stars":0,"title":"Reproducer for CVE-2026-85312 — Apache Camel camel-core saga hijacking via the Long-Running-Action header (CWE-20). Camel Spring Boot + Camel Quarkus."}],"tier":"poc_unverified"},"has_fix":false,"headline":"Apache Camel: Camel-Core Saga Participation Hijacking via the Unfiltered Long-Running-Action Header","id":"CVE-2026-85312","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"Security feature bypass in Apache Camel","id":"CVE-2026-85313"},"packages":[],"prev":{"headline":"WordPress MarketKing plugin \u003c= 2.1.60 - Broken Access Control vulnerability","id":"CVE-2026-85311"},"products":["Apache Camel"],"published":"2026-10-19","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Apache Software Foundation"]},"summary":"Attackers can hijack saga transactions by injecting an unfiltered header, requiring deployments using LRA coordinators to upgrade or strip the header.","url":"https://insights.sbomify.com/CVE-2026-85312/"}