CVE-2026-46453

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

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

Score 5.3 from GitHub Security Advisory published 2026-07-06. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
5.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 5.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Improper Input Validation, Authorization Bypass Through User-Controlled Key vulnerability in Apache Camel ElasticSearch Rest Client.

The camel-elasticsearch-rest-client component reads several Exchange headers to control its behaviour - SEARCH_QUERY (an advanced query body), OPERATION (which Elasticsearch operation to run), INDEX_NAME, INDEX_SETTINGS and ID. The string values of these header constants, defined in ElasticSearchRestClientConstant, are plain unprefixed names ('SEARCH_QUERY', 'OPERATION', 'INDEX_NAME', 'INDEX_SETTINGS', 'ID') rather than the 'Camel'-prefixed names used by every other Camel component (for example CamelSqlQuery, CamelMongoDbCriteria, CamelCqlQuery). Camel's inbound HTTP header filter, HttpHeaderFilterStrategy, blocks only header names that begin with 'Camel' or 'camel'. Because the Elasticsearch header names do not carry that prefix, they pass through the inbound filter unchanged. When a Camel route exposes an HTTP entry point (for example platform-http) in front of an elasticsearch-rest-client producer, an untrusted HTTP client can set these headers directly on its request and override the query and operation that the route author configured: reading every document in the index (SEARCH_QUERY with a match_all query), deleting documents (OPERATION set to Delete together with ID), or exfiltrating selected fields. No credentials are required and the producer reads the headers unconditionally. This issue affects Apache Camel: from 4.3.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0.

Users are recommended to upgrade to version 4.21.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.8. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.3. The fix renames the camel-elasticsearch-rest-client Exchange header constant string values (ID, SEARCH_QUERY, INDEX_SETTINGS, INDEX_NAME, OPERATION) to carry the Camel prefix (CamelElasticsearchId, CamelElasticsearchSearchQuery, CamelElasticsearchIndexSettings, CamelElasticsearchIndexName, CamelElasticsearchOperation) so that they are blocked by the inbound HttpHeaderFilterStrategy; the Java field names are unchanged. For deployments that cannot upgrade immediately, strip the affected headers from untrusted inbound messages before they reach the producer (for example removeHeader('SEARCH_QUERY'), removeHeader('OPERATION'), removeHeader('INDEX_NAME'), removeHeader('INDEX_SETTINGS') and removeHeader('ID') in front of the elasticsearch-rest-client endpoint), or apply a custom HeaderFilterStrategy that blocks these names.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
39
EG Risk 39/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 (value × EchelonGraph’s weight)
Severity53% × 45%
The EG Score, 5.3 of 10.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
44th
KEV
Not listed

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

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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

July 6, 2026

Last Modified

July 7, 2026

Advisory Details (2)

Auto-updated Jul 8, 2026
Patch available.
Web page

oss-security - CVE-2026-46453: Apache Camel: Camel-Elasticsearch-Rest-Client: Exchange header constants without the Camel prefix bypass inbound HTTP header filtering, allowing untrusted clients to override the Elasticsearch query and operation

http://www.openwall.com/lists/oss-security/2026/07/05/6
Web page

Apache Camel Security Advisory - CVE-2026-46453 - Apache Camel

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

Vendor Advisories for CVE-2026-46453(1)

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

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.apache.camel:camel-elasticsearch-rest-client4.19.0, 4.20.0
  • 4.3.0 up to 4.14.8: fixed in 4.14.8
  • 4.15.0 up to 4.18.3: fixed in 4.18.3
  • 4.19.0 up to 4.21.0: fixed in 4.21.0
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 31× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 100 of 177 refreshes 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 77 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-46453?
CVE-2026-46453 is a medium-severity vulnerability; its CVE record was published on July 6, 2026. Improper Input Validation, Authorization Bypass Through User-Controlled Key vulnerability in Apache Camel ElasticSearch Rest Client. The camel-elasticsearch-rest-client component reads several Exchange headers to control its behaviour - SEARCHQUERY (an advanced query body), OPERATION (which…
When was the CVE record for CVE-2026-46453 published?
The CVE record for CVE-2026-46453 was published on July 6, 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 July 7, 2026; the record at its source may have been updated since.
Is CVE-2026-46453 actively exploited?
CVE-2026-46453 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-46453?
CVE-2026-46453 has a CVSS v3.1 base score of 5.3 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-46453?
A fix for CVE-2026-46453 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-46453 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-46453

Explore →

Is Your Infrastructure Affected by CVE-2026-46453?

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

Book a Demo →Browse All CVEs