Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-48204 – Unauthenticated File Read, Deletion & NoSQL Injection – Apache Camel camel-mongo…

Be the first to know when new zero-days emerge:

Summary

CVE-2026-48204 is a critical Improper Input Validation and Improper Access Control vulnerability (CVSS 9.8) in the camel-mongodb-gridfs component of Apache Camel. Because the component’s control headers use plain, non-prefixed names that are not filtered at the HTTP boundary, any unauthenticated remote attacker can inject those headers into an inbound HTTP request and take full control of GridFS operations, including reading, deleting, and enumerating stored files, as well as injecting NoSQL operators into MongoDB queries. All Apache Camel deployments running an HTTP-consumer-to-GridFS route in the default (no explicit operation) configuration are affected.

Technical details

  • Root cause: The camel-mongodb-gridfs producer reads the GridFS operation to execute from the Exchange header gridfs.operation whenever the endpoint’s operation parameter is not set — which is the default. The underlying header constants (gridfs.operation, gridfs.objectid, gridfs.metadata, gridfs.chunksize, gridfs.fileid) do not carry the Camel/camel prefix. Because HttpHeaderFilterStrategy only blocks headers in the Camel namespace, these headers pass freely from an inbound HTTP request into the Exchange without any sanitisation.

  • Trigger conditions: A route that bridges any HTTP consumer component (e.g. platform-http, camel-servlet, camel-jetty, camel-undertow) into a mongodb-gridfs: producer without an explicit operation set on the endpoint — the default configuration.

  • Attack vector: An unauthenticated remote attacker sends an HTTP request with crafted headers to the exposed Camel endpoint. No credentials or user interaction are required.

  • Impact:

    • Arbitrary file deletion — set gridfs.operation: remove together with an attacker-chosen gridfs.objectid to delete any file in the GridFS bucket.

    • Full file enumeration — use gridfs.operation: listAll to retrieve a listing of every file in the bucket.

    • Arbitrary file read / data exfiltration — use gridfs.operation: findOne to read any file from the bucket, compromising confidentiality.

    • NoSQL operator injection — supply a MongoDB query operator in the gridfs.metadata header, which is parsed as a raw MongoDB document.

Affected software

  • Apache Camel (camel-mongodb-gridfs) 4.0.0 through 4.14.7

  • Apache Camel (camel-mongodb-gridfs) 4.15.0 through 4.18.2

  • Apache Camel (camel-mongodb-gridfs) 4.19.0 through 4.20.x

Severity

CVSS v3.1 Base Score: 9.8 (Critical) Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate — patch: Upgrade to one of the following fixed releases:

    • 4.21.0 (latest general release — recommended)

    • 4.14.8 (4.14.x LTS stream)

    • 4.18.3 (4.18.x maintenance stream)

  • Post-upgrade: Any route logic that drives GridFS operations or metadata via header names must be updated to use the new Camel-prefixed constants: CamelGridFsOperation, CamelGridFsObjectId, CamelGridFsMetadata, CamelGridFsChunkSize, and CamelGridFsFileId in place of the legacy gridfs.* names.

  • If immediate patching is not feasible:

    • Set an explicit operation parameter on every mongodb-gridfs: endpoint in your routes so that the operation is never derived from a request header.

    • Strip the gridfs.operation, gridfs.objectid, gridfs.metadata, gridfs.chunksize, and gridfs.fileid headers from all untrusted inbound traffic before the request reaches the GridFS producer.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.


WAF Mitigation ✨

Akamai App & API Protector

In Akamai Control Center (Security Configuration → your security policy → Custom Rules → Create a custom rule):

  • Rule logic: match ANY of the following (OR)

  • Add five conditions, each set to Request Header → header name → exists:

    • gridfs.operation

    • gridfs.objectid

    • gridfs.metadata

    • gridfs.chunksize

    • gridfs.fileid

You can also add this custom rule via Akamai API/CLI or the Akamai Custom Rule Builder Assistant:

{
  "name": "Apache-Camel-CVE-2026-48204-GridFS-header-block",
  "description": "Denies inbound requests smuggling internal Camel GridFS control headers (gridfs.operation, gridfs.objectid, gridfs.metadata, gridfs.chunksize, gridfs.fileid) into camel-mongodb-gridfs routes. CVE-2026-48204.",
  "structured": true,
  "operation": "OR",
  "conditions": [{
    "type": "requestHeaderMatch",
    "positiveMatch": true,
    "name": ["gridfs.operation", "gridfs.objectid", "gridfs.metadata", "gridfs.chunksize", "gridfs.fileid"],
    "nameWildcard": false,
    "value": ["*"],
    "valueWildcard": true,
    "valueCase": false
  }],
  "ruleActivated": true,
  "stagingOnly": false,
  "samplingRate": 100,
  "tag": ["CVE-2026-48204"]
}

Deploy to Akamai App & API Protector

Cloudflare WAF

Under Security → WAF → Custom rules → Create rule → "Edit expression":

any(lower(http.request.headers.names[*])[*] in {"gridfs.operation" "gridfs.objectid" "gridfs.metadata" "gridfs.chunksize" "gridfs.fileid"})

Deploy to Cloudflare WAF


⚠️ Note: WAF mitigation rules are in preview and not yet generally available.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge