Skip to content
VulniPulse
Medium 2 vendors · 2 advisories

CVE-2026-85312: Improper Input Validation vulnerability in Apache Camel Core component

CVE-2026-85312 key facts

CISA KEV
Not listed (catalogue checked )
Highest advisory rating
Medium
CVSS base score
4.8 (Apache), 4.8 (Red Hat)
Weakness
CWE-639
Fixed releases
  • Apache: 4.18.5, 4.22.1
  • Red Hat: 4.23.0, 4.18, 4.18.5, 4.22, 4.22.1
Vendor advisories
2 from Apache, Red Hat
Listed by VulniPulse
Record changed

Ratings, versions and fixes are quoted from the vendor advisories that cover only CVE-2026-85312; each belongs to its advisory, not to every product listed. How records are collected and checked.

How do I fix CVE-2026-85312?

Upgrade to a fixed release named by the vendor:

  • Apache: 4.18.5, 4.22.1
  • Red Hat: 4.23.0, 4.18, 4.18.5, 4.22, 4.22.1
  • Upgrade to Apache Camel 4.23.0, which fixes the issue. (Apache)
  • Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. (Apache)

Vendor advisories for CVE-2026-85312

Apache

1 advisory
  • Advisory severityMedium4.8

    Medium [CVE-2026-85312] Improper Input Validation vulnerability in Apache Camel Core component

    CVE-2026-85312Source published Source updated

    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…

    Affected products in this advisory
    • Apache Camel Core
    Source-reported affected versions
    • 4.0.0 before 4.18.5
    • 4.19.0 before 4.22.1
    Source-reported fixed versions
    • 4.18.5
    • 4.22.1
    Mitigation guidance
    • 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.
    • 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.
    Workarounds
    • 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.

Red Hat

1 advisory
  • Advisory severityMedium4.8

    Medium [CVE-2026-85312] Unauthorized transaction association via unfiltered message header

    CVE-2026-85312Source published Source updated

    Unauthorized transaction association via unfiltered message header. Red Hat rates this moderate (CVSS 4.8). Weakness: CWE-639. Affected products named by the advisory: Red Hat build of Apache Camel for Spring Boot 4; Red Hat Fuse 7.

    Related products — impact not confirmed
    • Red Hat build of Apache Camel for Spring Boot 4
    • Red Hat Fuse 7
    Source-reported affected versions
    • < 4.0.0
    • < 4.18.5
    • < 4.19.0
    • < 4.22.1
    Source-reported fixed versions
    • 4.23.0
    • 4.18
    • 4.18.5
    • 4.22

    1 more entries in the full advisory.

    Mitigation guidance
    No mitigation guidance extracted; consult the source.

References

All Apache advisories

Get an email when Apache publishes the next one.

See Apache's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).

Alert me about Apache

iPhone and Android apps · New on the App Store

Get alerts for new CVEs on your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery