Skip to content
Noroxi
CVE.org (no NVD analysis yet)· CNA apache

CVE-2026-85312: Apache Camel: Camel-Core Saga Participation Hijacking via the Unfiltered Long-Running-Action Header

MediumCVSS 4.8 · v3.1—Proof of concept Fix available

Noroxi assessment

Priority: Monitor (action score 19/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.53% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: Apache Software Foundation Apache Camel 4.18.5, 4.22.1.

Low priority for now. Upgrade to Apache Software Foundation Apache Camel 4.18.5, 4.22.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Oct 19, 2026
Updated
Nov 3, 2026
EPSS
0.5% · 45th percentile

Report tools

JSON

Action score

19

Monitor

Low priority for now.

CVSS
19 / 40 · 4.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · apache
4.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-85312

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for apache records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
apachecamel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.

  • Apache Software Foundation Apache Camel

    • 4.18.5, 4.22.1, 4.23.0not affected
    • 4.0.0 and later · before 4.18.5affected · maven
    • 4.19.0 and later · before 4.22.1affected · maven

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • apache camel4.0.0 and later · before 4.18.5
  • apache camel4.19.0 and later · before 4.22.1

Same product

apache: all records

Other highest-scoring records for the same primary product.

  • CVE-2025-27636Apache Camel: Camel Message Header Injection via Improper Filtering
    51Plan
  • CVE-2026-47323Apache Camel: Camel-CXF Message Header Injection via Missing Inbound Filtering
    45Plan
  • CVE-2026-33453Apache Camel: CoAP URI Query Parameter to Exchange Header Injection in camel-coap Allows Single-Packet Pre-Auth Remote Code Execution
    43Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-85260Oct 19, 2026 · Apache Camel: Camel-MLLP Protected Health Information Disclosure to Logs by Default
    22Monitor
  • ← EarlierCVE-2026-85296Oct 19, 2026 · Apache Camel: Camel-AS2 Cross-Partner Signing Key Confusion via Shared Per-Request State
    26Monitor
  • Later →CVE-2026-85313Oct 19, 2026 · Apache Camel: Camel-Jetty Cross-Origin Credential Exposure via Allow-All CrossOriginFilter Defaults When enableCORS Is Set
    17Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Apache Software Foundation Apache Camel4.18.5Vendor (CNA)
Apache Software Foundation Apache Camel4.22.1Vendor (CNA)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:02026-10-20

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. Fix recordedsame day
  3. First PoC+1 d
  4. TodayNov 12, 2026+24 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-7130056 days apartApache Camel: Camel-Atmosphere-Websocket: WebSocket dispatch header injection
    39Monitor
  • CVE-2026-7832956 days apartApache Camel: Camel-Undertow: the endpoint discarded the undertow-specific header filter strategy in favour of the base HTTP one, so the undertow filtering…
    39Monitor
  • CVE-2026-46454105 days apartApache Camel: Camel-Cometd: Inbound Bayeux message headers are mapped into the Exchange without a HeaderFilterStrategy, allowing unauthenticated clients to…
    39Monitor
  • CVE-2026-46456105 days apartApache Camel: Camel-AWS2-SQS: Inbound message attributes are mapped into the Exchange without an inbound HeaderFilterStrategy, allowing a message sender to…
    39Monitor
  • CVE-2026-48204105 days apartApache Camel: Camel-MongoDB-GridFS: The gridfs.* control headers used non-Camel-prefixed names that bypass the HTTP header filter, allowing an HTTP client to…
    39Monitor
  • CVE-2026-56140105 days apartApache Camel AWS2 SNS: An inbound Camel-namespace filter was added to Sns2HeaderFilterStrategy to align it with sibling components
    39Monitor

Not on record for this CVE: public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
low · data can be read
Integrity
low · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
Low
Availability impact
None

Weakness class (CWE)

CWE-20 · Improper Input Validation

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Exploit maturitynone → poc
  2. SSVC exploitation— → none
  3. Exploit maturity— → none
  4. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records