CVE-2026-40453

CRITICALPre-NVD 9.99.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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 (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory

Also known asEUVD-2026-25791 (ENISA EUVD) · GHSA-jg2m-9x48-3gvj (GitHub Security Advisories)Source: ENISA EUVD

9.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2.1%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 impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity99% × 45%
Impact severity (EG Severity): CVSS 9.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation2.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
2.1%
EPSS %ILE
82nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.9): severity, escalated by confirmed exploitation. This CVE's 9.9 is its impact severity (EG Severity), not escalated.

EG Severity
9.9 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
2.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 27, 2026

Last Modified

October 26, 2026

Advisory Details (6)

Auto-updated Nov 2, 2026
Patch available. Sources: redhat.
Red HatMentions 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
Red HatMentions 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
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:19835
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:17668
Web page

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

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

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatcamel-jms2026-05-20redhat
mavenorg.apache.camel:camel-coap @ 4.14.6 (fixes >= 3.0.0, < 4.14.6)—ghsa
mavenorg.apache.camel:camel-coap @ 4.18.2 (fixes >= 4.15.0, < 4.18.2)—ghsa
mavenorg.apache.camel:camel-coap @ 4.20.0 (fixes >= 4.19.0, < 4.20.0)—ghsa

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 21× in last 7d / 73× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 408 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 308 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:52 UTCEPSS rescoreEPSS 2.1% · 82nd percentile
  2. 2026-11-13 05:18 UTCEchelonGraph re-scored
  3. 2026-11-13 05:18 UTCVendor advisory
  4. 2026-11-13 05:18 UTCGHSA enrichmentGHSA-jg2m-9x48-3gvj · GitHub severity CRITICAL · GitHub CVSS 9.9
  5. 2026-11-12 16:33 UTCEPSS rescoreEPSS 2.1% · 82nd percentile
  6. 2026-11-12 04:55 UTCEchelonGraph re-scored
  7. 2026-11-12 04:55 UTCVendor advisory
  8. 2026-11-12 04:55 UTCGHSA enrichmentGHSA-jg2m-9x48-3gvj · GitHub severity CRITICAL · GitHub CVSS 9.9
  9. 2026-11-11 16:39 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  10. 2026-11-11 04:32 UTCEchelonGraph re-scored
  11. 2026-11-11 04:32 UTCVendor advisory
  12. 2026-11-11 04:32 UTCGHSA enrichmentGHSA-jg2m-9x48-3gvj · GitHub severity CRITICAL · GitHub CVSS 9.9
  13. 2026-11-10 16:43 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  14. 2026-11-10 04:08 UTCEchelonGraph re-scored
  15. 2026-11-10 04:08 UTCVendor advisory
  16. 2026-11-10 04:08 UTCGHSA enrichmentGHSA-jg2m-9x48-3gvj · GitHub severity CRITICAL · GitHub CVSS 9.9
  17. 2026-11-09 16:35 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  18. 2026-11-09 03:43 UTCEchelonGraph re-scored
  19. 2026-11-09 03:43 UTCVendor advisory
  20. 2026-11-09 03:42 UTCGHSA enrichmentGHSA-jg2m-9x48-3gvj · GitHub severity CRITICAL · GitHub CVSS 9.9
  21. 2026-11-08 16:39 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  22. 2026-11-08 03:19 UTCEchelonGraph re-scored
  23. 2026-11-08 03:19 UTCVendor advisory
  24. 2026-11-08 03:19 UTCGHSA enrichmentGHSA-jg2m-9x48-3gvj · GitHub severity CRITICAL · GitHub CVSS 9.9
  25. 2026-11-07 16:39 UTCEPSS rescoreEPSS 2.1% · 81st percentile
Show 75 more
  1. 2026-11-07 02:56 UTCEchelonGraph re-scored
  2. 2026-11-07 02:56 UTCVendor advisory
  3. 2026-11-07 02:56 UTCGHSA enrichmentGHSA-jg2m-9x48-3gvj · GitHub severity CRITICAL · GitHub CVSS 9.9
  4. 2026-11-06 16:37 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  5. 2026-11-06 07:55 UTCOSV refresh
  6. 2026-11-06 02:33 UTCEchelonGraph re-scored
  7. 2026-11-06 02:33 UTCVendor advisory
  8. 2026-11-06 02:33 UTCGHSA enrichmentGHSA-jg2m-9x48-3gvj · GitHub severity CRITICAL · GitHub CVSS 9.9
  9. 2026-11-05 16:37 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  10. 2026-11-05 02:10 UTCEchelonGraph re-scored
  11. 2026-11-05 02:10 UTCVendor advisory
  12. 2026-11-05 02:10 UTCGHSA enrichmentGHSA-jg2m-9x48-3gvj · GitHub severity CRITICAL · GitHub CVSS 9.9
  13. 2026-11-04 16:35 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  14. 2026-11-04 01:47 UTCEchelonGraph re-scored
  15. 2026-11-04 01:47 UTCVendor advisory
  16. 2026-11-04 01:47 UTCGHSA enrichmentGHSA-jg2m-9x48-3gvj · GitHub severity CRITICAL · GitHub CVSS 9.9
  17. 2026-11-03 16:48 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  18. 2026-11-03 01:23 UTCEchelonGraph re-scored
  19. 2026-11-03 01:23 UTCVendor advisory
  20. 2026-11-03 01:23 UTCGHSA enrichmentGHSA-jg2m-9x48-3gvj · GitHub severity CRITICAL · GitHub CVSS 9.9
  21. 2026-11-02 16:44 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  22. 2026-11-02 00:51 UTCEchelonGraph re-scored
  23. 2026-11-02 00:51 UTCVendor advisory
  24. 2026-11-02 00:51 UTCGHSA enrichmentGHSA-jg2m-9x48-3gvj · GitHub severity CRITICAL · GitHub CVSS 9.9
  25. 2026-11-01 16:34 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  26. 2026-11-01 00:28 UTCEchelonGraph re-scored
  27. 2026-11-01 00:28 UTCVendor advisory
  28. 2026-10-31 16:32 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  29. 2026-10-31 00:05 UTCEchelonGraph re-scored
  30. 2026-10-31 00:05 UTCVendor advisory
  31. 2026-10-30 16:34 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  32. 2026-10-29 23:42 UTCEchelonGraph re-scored
  33. 2026-10-29 23:42 UTCVendor advisory
  34. 2026-10-29 16:33 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  35. 2026-10-28 23:19 UTCEchelonGraph re-scored
  36. 2026-10-28 23:19 UTCVendor advisory
  37. 2026-10-28 16:32 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  38. 2026-10-27 22:52 UTCEchelonGraph re-scored
  39. 2026-10-27 22:52 UTCVendor advisory
  40. 2026-10-27 16:31 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  41. 2026-10-26 22:28 UTCVendor advisory
  42. 2026-10-26 21:28 UTCEchelonGraph re-scored
  43. 2026-10-26 21:28 UTCVendor advisory
  44. 2026-10-26 16:31 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  45. 2026-10-25 23:47 UTCEchelonGraph re-scored
  46. 2026-10-25 23:47 UTCVendor advisory
  47. 2026-10-25 16:32 UTCEPSS rescoreEPSS 2.1% · 81st percentile
  48. 2026-10-25 14:31 UTCEchelonGraph re-scored
  49. 2026-10-24 23:16 UTCEchelonGraph re-scored
  50. 2026-10-24 23:16 UTCVendor advisory
  51. 2026-10-24 16:32 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  52. 2026-10-23 22:53 UTCEchelonGraph re-scored
  53. 2026-10-23 22:53 UTCVendor advisory
  54. 2026-10-23 16:31 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  55. 2026-10-22 22:13 UTCEchelonGraph re-scored
  56. 2026-10-22 22:13 UTCVendor advisory
  57. 2026-10-22 16:34 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  58. 2026-10-21 21:50 UTCEchelonGraph re-scored
  59. 2026-10-21 21:50 UTCVendor advisory
  60. 2026-10-21 16:33 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  61. 2026-10-20 21:23 UTCEchelonGraph re-scored
  62. 2026-10-20 21:23 UTCVendor advisory
  63. 2026-10-20 16:33 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  64. 2026-10-19 21:00 UTCEchelonGraph re-scored
  65. 2026-10-19 21:00 UTCVendor advisory
  66. 2026-10-19 16:32 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  67. 2026-10-18 19:39 UTCEchelonGraph re-scored
  68. 2026-10-18 19:39 UTCVendor advisory
  69. 2026-10-18 16:32 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  70. 2026-10-18 03:42 UTCEchelonGraph re-scored
  71. 2026-10-17 19:16 UTCEchelonGraph re-scored
  72. 2026-10-17 19:16 UTCVendor advisory
  73. 2026-10-17 16:34 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  74. 2026-10-16 18:53 UTCEchelonGraph re-scored
  75. 2026-10-16 18:53 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-40453?
CVE-2026-40453 is a critical-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-40453 published?
The CVE record for CVE-2026-40453 was published on April 27, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 26, 2026; the record at its source may have been updated since.
Is CVE-2026-40453 actively exploited?
CVE-2026-40453 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.1% probability of exploitation in the next 30 days (82nd 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.