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: 1.9%CVSS: 9.9Exploit: None knownExposed services: Not assessed

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.9CRITICALmedium confidence
EG Risk
45
EG Risk 45/100

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%
EPSS PROB
1.9%
EPSS %ILE
78th
KEV
Not listed

Published

April 27, 2026

Last Modified

July 15, 2026

Advisory Details (6)

Auto-updated Oct 8, 2026
Patch available. Sources: redhat.
redhatMentions a patch (unverified)

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
redhatMentions a patch (unverified)

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
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:19835
redhatMentions a patch (unverified)
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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / 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 rangeFix by version rangeDependents
org.apache.camel:camel-coap4.19.0
  • 3.0.0 up to 4.14.6: fixed in 4.14.6
  • 4.15.0 up to 4.18.2: fixed in 4.18.2
  • 4.19.0 up to 4.20.0: fixed in 4.20.0
—
org.apache.camel:camel-google-pubsub4.19.0
  • 3.0.0 up to 4.14.6: fixed in 4.14.6
  • 4.15.0 up to 4.18.2: fixed in 4.18.2
  • 4.19.0 up to 4.20.0: fixed in 4.20.0
—
org.apache.camel:camel-jms4.19.0
  • 3.0.0 up to 4.14.6: fixed in 4.14.6
  • 4.15.0 up to 4.18.2: fixed in 4.18.2
  • 4.19.0 up to 4.20.0: fixed in 4.20.0
—
org.apache.camel:camel-sjms4.19.0
  • 3.0.0 up to 4.14.6: fixed in 4.14.6
  • 4.15.0 up to 4.18.2: fixed in 4.18.2
  • 4.19.0 up to 4.20.0: fixed in 4.20.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 24× 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 290 total refreshes for this CVE.

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

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 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 1.9% probability of exploitation in the next 30 days (78th percentile of EPSS-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?
A fix for CVE-2026-40453 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-40453 are linked in the Vendor Advisories panel on this page.

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.