CVE-2026-40453

CRITICALPre-NVD 9.99.9—
EchelonGraph scoreMEDIUM confidence

Score 9.9 from GitHub Security Advisory (severity: CRITICAL) published 2026-04-27. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
9.9EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2%CVSS: 9.9Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
9.9
EG Score
9.9(medium)
EG Risk
45(Track)
EG Risk 45/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity99% × 45%
Exploitation2% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
2%
EPSS %ILE
73%
KEV
Not listed

Published

April 27, 2026

Last Modified

July 15, 2026

Advisory Details (6)

Auto-updated Aug 20, 2026
Patch available. Sources: redhat.
redhat Patch Available
https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-40453.json
redhat Patch Available

2463173 – (CVE-2026-40453) CVE-2026-40453 Apache Camel: org.apache.camel: Apache Camel: Remote Code Execution and Arbitrary File Write via case-variant header injection

https://bugzilla.redhat.com/show_bug.cgi?id=2463173
redhat Patch Available

CVE-2026-40453 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-40453
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:19835
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:17668
generic

Apache Camel Security Advisory - CVE-2026-40453 - Apache Camel

https://camel.apache.org/security/CVE-2026-40453.html

Vendor Advisories for CVE-2026-40453(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatcamel-jms2026-05-20redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 1 ecosystem)
Maven(4)
PackageVulnerable rangeFixed inDependents
org.apache.camel:camel-coap4.19.04.20.0—
org.apache.camel:camel-google-pubsub4.19.04.20.0—
org.apache.camel:camel-jms4.19.04.20.0—
org.apache.camel:camel-sjms4.19.04.20.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 86× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 253 total refreshes for this CVE.

  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-23 00:19 UTCEPSS rescore
  3. 2026-08-21 23:49 UTCEPSS rescore
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-19 17:03 UTCEPSS rescore
  6. 2026-08-18 13:48 UTCEPSS rescore
  7. 2026-08-17 14:06 UTCEG score recompute
  8. 2026-08-17 14:06 UTCVendor advisory
  9. 2026-08-17 13:47 UTCEPSS rescore
  10. 2026-08-16 14:56 UTCEPSS rescore
  11. 2026-08-16 10:01 UTCVendor advisory
  12. 2026-08-16 05:39 UTCEG score recompute
  13. 2026-08-16 05:39 UTCVendor advisory
  14. 2026-08-16 02:14 UTCEPSS rescore
  15. 2026-08-15 01:45 UTCEG score recompute
  16. 2026-08-15 01:45 UTCVendor advisory
  17. 2026-08-15 01:30 UTCEPSS rescore
  18. 2026-08-14 21:24 UTCVendor advisory
  19. 2026-08-14 17:03 UTCVendor advisory
  20. 2026-08-14 12:43 UTCVendor advisory
  21. 2026-08-14 08:22 UTCVendor advisory
  22. 2026-08-14 04:02 UTCEG score recompute
  23. 2026-08-14 04:02 UTCVendor advisory
  24. 2026-08-13 22:00 UTCEPSS rescore
  25. 2026-08-13 08:27 UTCVendor advisory
Show 75 more
  1. 2026-08-13 02:24 UTCVendor advisory
  2. 2026-08-12 22:03 UTCVendor advisory
  3. 2026-08-12 17:43 UTCEG score recompute
  4. 2026-08-12 17:43 UTCVendor advisory
  5. 2026-08-12 13:51 UTCEPSS rescore
  6. 2026-08-12 01:21 UTCVendor advisory
  7. 2026-08-11 21:00 UTCVendor advisory
  8. 2026-08-11 16:39 UTCEG score recompute
  9. 2026-08-11 16:39 UTCVendor advisory
  10. 2026-08-11 13:43 UTCEPSS rescore
  11. 2026-08-11 06:25 UTCVendor advisory
  12. 2026-08-11 02:03 UTCEG score recompute
  13. 2026-08-11 02:03 UTCVendor advisory
  14. 2026-08-11 00:00 UTCEPSS rescore
  15. 2026-08-10 10:21 UTCVendor advisory
  16. 2026-08-10 06:00 UTCVendor advisory
  17. 2026-08-10 01:40 UTCVendor advisory
  18. 2026-08-09 21:18 UTCVendor advisory
  19. 2026-08-09 16:57 UTCEG score recompute
  20. 2026-08-09 16:57 UTCVendor advisory
  21. 2026-08-09 13:46 UTCEPSS rescore
  22. 2026-08-09 12:37 UTCVendor advisory
  23. 2026-08-09 07:34 UTCVendor advisory
  24. 2026-08-09 03:13 UTCEG score recompute
  25. 2026-08-09 03:13 UTCVendor advisory
  26. 2026-08-08 16:37 UTCEPSS rescore
  27. 2026-08-08 10:08 UTCVendor advisory
  28. 2026-08-08 05:47 UTCVendor advisory
  29. 2026-08-08 01:27 UTCVendor advisory
  30. 2026-08-07 21:06 UTCVendor advisory
  31. 2026-08-07 16:45 UTCEG score recompute
  32. 2026-08-07 16:45 UTCVendor advisory
  33. 2026-08-07 12:25 UTCVendor advisory
  34. 2026-08-06 21:31 UTCVendor advisory
  35. 2026-08-06 17:10 UTCEG score recompute
  36. 2026-08-06 17:10 UTCVendor advisory
  37. 2026-08-06 13:46 UTCEPSS rescore
  38. 2026-08-06 11:53 UTCVendor advisory
  39. 2026-08-06 07:32 UTCVendor advisory
  40. 2026-08-06 03:12 UTCVendor advisory
  41. 2026-08-05 22:51 UTCEG score recompute
  42. 2026-08-05 22:51 UTCVendor advisory
  43. 2026-08-05 19:17 UTCEPSS rescore
  44. 2026-08-04 15:10 UTCEPSS rescore
  45. 2026-08-04 10:38 UTCEPSS rescore
  46. 2026-08-04 05:38 UTCVendor advisory
  47. 2026-08-04 01:15 UTCVendor advisory
  48. 2026-08-03 20:55 UTCEG score recompute
  49. 2026-08-03 20:55 UTCVendor advisory
  50. 2026-08-03 10:36 UTCEPSS rescore
  51. 2026-08-02 23:30 UTCVendor advisory
  52. 2026-08-02 19:09 UTCVendor advisory
  53. 2026-08-02 14:48 UTCVendor advisory
  54. 2026-08-02 10:27 UTCEG score recompute
  55. 2026-08-02 10:27 UTCVendor advisory
  56. 2026-08-02 02:27 UTCEPSS rescore
  57. 2026-08-01 04:16 UTCEPSS rescore
  58. 2026-07-30 16:28 UTCEPSS rescore
  59. 2026-07-30 01:30 UTCEPSS rescore
  60. 2026-07-28 15:36 UTCEPSS rescore
  61. 2026-07-27 14:13 UTCEPSS rescore
  62. 2026-07-26 14:54 UTCEPSS rescore
  63. 2026-07-26 14:54 UTCEPSS rescore
  64. 2026-07-25 14:18 UTCEPSS rescore
  65. 2026-07-25 14:18 UTCEPSS rescore
  66. 2026-07-24 14:17 UTCEPSS rescore
  67. 2026-07-24 14:17 UTCEPSS rescore
  68. 2026-07-23 14:18 UTCEPSS rescore
  69. 2026-07-23 14:18 UTCEPSS rescore
  70. 2026-07-23 03:11 UTCEG score recompute
  71. 2026-07-22 14:08 UTCEPSS rescore
  72. 2026-07-21 15:24 UTCEPSS rescore
  73. 2026-07-20 22:02 UTCOSV refresh
  74. 2026-07-20 17:08 UTCEPSS rescore
  75. 2026-07-19 14:31 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-40453?
CVE-2026-40453 is a critical vulnerability published on April 27, 2026. 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…
When was CVE-2026-40453 disclosed?
CVE-2026-40453 was first published in the National Vulnerability Database on April 27, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-40453 actively exploited?
CVE-2026-40453 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2% probability of exploitation in the next 30 days, which ranks it in the top 26.7% of all scored CVEs.
What is the CVSS score of CVE-2026-40453?
CVE-2026-40453 has a CVSS v3.1 base score of 9.9 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-40453?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-40453, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-40453

Explore →

Is Your Infrastructure Affected by CVE-2026-40453?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs