CVE-2026-48204

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

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

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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Improper Input Validation, Improper Access Control vulnerability in Apache Camel in Camel Mongodb Gridfs component.

The camel-mongodb-gridfs producer selects the GridFS operation to perform from the gridfs.operation Exchange header when the endpoint's operation parameter is not set - which is the default. The control-header constants (GridFsConstants.GRIDFS_OPERATION, GRIDFS_OBJECT_ID, GRIDFS_METADATA, GRIDFS_CHUNKSIZE, GRIDFS_FILE_ID_PRODUCED) were the plain strings gridfs.operation, gridfs.objectid, gridfs.metadata, gridfs.chunksize and gridfs.fileid. Because these names do not start with the Camel / camel prefix, HttpHeaderFilterStrategy - which blocks only the Camel header namespace on the HTTP boundary - let them pass from an inbound HTTP request straight into the Exchange. In a route that bridges an HTTP consumer (for example platform-http) into a mongodb-gridfs: producer with no explicit operation, any HTTP client could therefore set the gridfs.operation header to override the route's intended operation - switching, for example, a file upload to remove (deleting a file identified by the attacker-supplied gridfs.objectid), listAll (enumerating every file in the bucket) or findOne (reading a file) - and supply a gridfs.metadata value that is parsed as a MongoDB document, enabling NoSQL operator injection. No credentials are required when the bridging consumer is unauthenticated. This issue affects Apache Camel: from 4.0.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. After upgrading, routes that drive GridFS operations or metadata via the raw header names must use CamelGridFsOperation / CamelGridFsObjectId / CamelGridFsMetadata / CamelGridFsChunkSize / CamelGridFsFileId instead of the gridfs.* names. For deployments that cannot upgrade immediately, set an explicit operation on the mongodb-gridfs: endpoint so the operation is not taken from a header, and strip the gridfs.* headers from any untrusted ingress before the producer.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
59(Track)
EG Risk 59/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
Severity98% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
52%
KEV
Not listed

Published

July 6, 2026

Last Modified

July 8, 2026

Advisory Details (2)

Auto-updated Sep 6, 2026
No patch confirmed yet.
generic

oss-security - CVE-2026-48204: Apache Camel: Camel-MongoDB-GridFS: The gridfs.* control headers used non-Camel-prefixed names that bypass the HTTP header filter, allowing an HTTP client to switch the GridFS operation - including destructive file deletion - in the default configuration

http://www.openwall.com/lists/oss-security/2026/07/05/18
generic

Apache Camel Security Advisory - CVE-2026-48204 - Apache Camel

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

Vendor Advisories for CVE-2026-48204(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 rangeFixed inDependents
org.apache.camel:camel-mongodb-gridfs4.19.0, 4.20.04.21.0—

Weakness Classification(2)

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

Data Freshness Timeline

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

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-48204?
CVE-2026-48204 is a critical vulnerability published on July 6, 2026. Improper Input Validation, Improper Access Control vulnerability in Apache Camel in Camel Mongodb Gridfs component. The camel-mongodb-gridfs producer selects the GridFS operation to perform from the gridfs.operation Exchange header when the endpoint's operation parameter is not set - which is the…
When was CVE-2026-48204 disclosed?
CVE-2026-48204 was first published in the National Vulnerability Database on July 6, 2026, with the most recent update on July 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48204 actively exploited?
CVE-2026-48204 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 47.8% of all scored CVEs.
What is the CVSS score of CVE-2026-48204?
CVE-2026-48204 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-48204?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48204, 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-48204

Explore →

Is Your Infrastructure Affected by CVE-2026-48204?

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

Start Free Scan →Browse All CVEs