CVE-2026-40453

CRITICALPre-NVD 9.99.9—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
9.9
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.9Exploit: NoneExposed: 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)
EPSS
54.2%
KEV
Not listed

Published

April 27, 2026

Last Modified

June 29, 2026

Advisory Details (1)

Auto-updated Jul 7, 2026
No patch confirmed yet.
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 9× in last 7d / 49× 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 213 total refreshes for this CVE.

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

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 June 29, 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 54.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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