LiveActive security incident?Get immediate response
CVE Record

CVE-2026-40453: Apache Camel JMS, Apache Camel CoAP, Apache Camel Google PubSub: Incomplete fix for CVE-2025-27636 in non-HTTP HeaderFilterStrategies (camel-jms, camel-sjms, camel-coap, camel-google-pubsub) allows case-variant header injection

The fix for CVE-2025-27636 added setLowerCase(true) to HttpHeaderFilterStrategy so that case-variant header names such as 'CAmelExecCommandExecutable' are filtered out alongside 'CamelExecCommandExecutable'. The same setLowerCase(true) call was not applied to five non-HTTP HeaderFilterStrategy implementations: JmsHeaderFilterStrategy and ClassicJmsHeaderFilterStrategy in camel-jms, SjmsHeaderFilterStrategy in camel-sjms, CoAPHeaderFilterStrategy in camel-coap, and GooglePubsubHeaderFilterStrategy in camel-google-pubsub. Because those strategies use case-sensitive String.startsWith('Camel'/'camel') filtering while the Camel Exchange stores headers in a case-insensitive map, an attacker with JMS (or equivalent) producer access to the broker consumed by a Camel route can inject case-variant Camel internal headers, which are then resolved by downstream components such as camel-exec and camel-file using their canonical casing. This enables remote code execution and arbitrary file write on routes that forward JMS messages to header-driven components. This issue affects Apache Camel: from 3.0.0 before 4.14.6, from 4.15.0 before 4.18.2, from 4.19.0 before 4.20.0. Users are recommended to upgrade to version 4.20.0, which fixes the issue. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.6. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.2.

CriticalCVSS 9.9Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Apache Camel can fail to block case-variant internal headers on some non-HTTP messaging components. An attacker who can publish messages to a broker or equivalent source consumed by Camel may smuggle headers that downstream routes trust, potentially causing command execution or file writes.

Executive priority

Treat as urgent for integration platforms that consume externally supplied messages. Prioritize internet-adjacent or partner-facing brokers first, because successful exploitation can cross from message submission into code execution or arbitrary file write on affected routes.

Technical view

CVE-2026-40453 is an incomplete fix for CVE-2025-27636. Several non-HTTP HeaderFilterStrategy implementations did not lowercase header names before filtering Camel internal headers. Because Exchange headers are case-insensitive, case variants can bypass filtering and later resolve to canonical internal headers.

Likely exposure

Systems using vulnerable Apache Camel versions with camel-jms, camel-sjms, camel-coap, or camel-google-pubsub routes are most exposed, especially where untrusted or semi-trusted producers can send messages into routes that forward to header-driven components.

Exploitation context

The source bundle does not cite active exploitation, and KEV is false. Exploitation requires producer access to JMS or an equivalent consumed channel, plus a route path where injected internal headers influence downstream components such as camel-exec or camel-file.

Researcher notes

Focus review on non-HTTP HeaderFilterStrategy behavior and case-insensitive Exchange header resolution. The vulnerable pattern is case-sensitive filtering of Camel internal header prefixes before downstream components interpret canonical header names. Evidence is strongest for the affected versions and components named by Apache.

Mitigation direction

  • Upgrade Apache Camel to 4.20.0 where possible.
  • Use 4.14.6 for the 4.14.x LTS stream.
  • Use 4.18.2 for the 4.18.x release stream.
  • Restrict producer access to brokers and equivalent consumed channels.
  • Review vendor guidance for Red Hat-packaged Camel deployments.

Validation and detection

  • Inventory Camel dependencies for camel-jms, camel-sjms, camel-coap, and camel-google-pubsub.
  • Identify versions in affected ranges before 4.14.6, 4.18.2, or 4.20.0.
  • Review routes that pass external messages into header-driven components.
  • Confirm broker or channel producer permissions are limited to trusted principals.
  • Check Red Hat advisories if using Red Hat distributions.
Prepared
Confidence
high
Sources
8

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-178: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-40453 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.9 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
7Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.9CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H3.16CISA-ADP
9.9CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H3.16redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

9.9Critical
CVSS 3.1 vector shape for CVE-2026-40453Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
redhat-SADPApache Camel: org.apache.camel: Apache Camel: Remote Code Execution and Arbitrary File Write via case-variant header injection
other:Red Hat severity ratingcvssV3_1
  • 2026-04-27T10:01:14.347Z: Reported to Red Hat.
  • 2026-04-27T08:23:20.354Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Apache Software FoundationApache Camel JMSorg.apache.camel:camel-jms, 3.0.0, 4.15.0, 4.19.0unaffected
Apache Software FoundationApache Camel CoAPorg.apache.camel:camel-coap, 3.0.0, 4.15.0, 4.19.0unaffected
Apache Software FoundationApache Camel Google PubSuborg.apache.camel:camel-google-pubsub, 3.0.0, 4.15.0, 4.19.0unaffected
Weakness

CWE details

CWE-178

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-178 · source CWE mapping

Improper Handling of Case Sensitivity

Improper Handling of Case Sensitivity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs