Response playbooks, investigation guides, and Atomic Red Team tests are Pro-only. Upgrade to unlock the full detection package for CVE-2026-48204.

Upgrade to Pro
CVE-2026-48204

Apache Camel camel-mongodb-gridfs Header Injection / GridFS Operation Override (CVE-2026-48204)

Detects exploitation attempts against CVE-2026-48204, a critical (CVSS 9.8) input validation flaw (CWE-20) in the Apache Camel camel-mongodb-gridfs component. Affected versions (>=4.0.0 <4.14.8, >=4.15.0 <4.18.3, >=4.19.0 <4.21.0) fail to filter caller-supplied gridfs.* HTTP/Camel exchange headers before applying them to GridFS producer operations, allowing an attacker to override the intended GridFS operation (e.g. force a delete/listAll/findOne instead of the intended write) and inject NoSQL query operators into MongoDB GridFS filter queries. This can lead to unauthorized data disclosure, deletion of stored files, or NoSQL injection against the backing MongoDB metadata collection. A public PoC/advisory exists (GHSA-f7g3-2cg6-f5hj).

Vulnerability Intelligence

Public PoC

CVSS

9.8
Critical (9.0–10)

CVSS vector not yet published

Read the write-up →

What is CVE-2026-48204 Apache Camel camel-mongodb-gridfs Header Injection / GridFS Operation Override (CVE-2026-48204)?

Apache Camel camel-mongodb-gridfs Header Injection / GridFS Operation Override (CVE-2026-48204) (CVE-2026-48204) maps to the Initial Access and Defense Evasion and Impact tactics — the adversary is trying to get into your network in MITRE ATT&CK.

This page provides production-ready detection logic for Apache Camel camel-mongodb-gridfs Header Injection / GridFS Operation Override (CVE-2026-48204), covering the data sources and telemetry it touches: Azure App Service HTTP Logs, Web Application Firewall Logs, Reverse Proxy Logs. The queries below are rated critical severity at medium confidence, and ship for 7 SIEM platforms — KQL, SPL, Elastic, QRadar, Sumo, YARA-L, LogScale.

MITRE ATT&CK

Tactic
Initial Access Defense Evasion Impact
Microsoft Sentinel / Defender
kusto
let SuspiciousHeaders = dynamic(["gridfs.operation", "gridfs.query", "gridfs.filter", "gridfs.$where", "gridfs.delete", "gridfs.remove"]);
AppServiceHTTPLogs
| where TimeGenerated > ago(24h)
| where CsHost has "camel" or CsUriStem has "gridfs" or CsUriStem has "camel"
| extend HeaderMatches = extract_all(@"(?i)(gridfs\.[a-zA-Z\$]+)\s*[:=]", RequestHeaders)
| where array_length(HeaderMatches) > 0 or RequestHeaders has "$where" or RequestHeaders has "$ne" or RequestHeaders has "$gt" or RequestHeaders has "$regex"
| project TimeGenerated, CIp, CsHost, CsUriStem, RequestHeaders, HeaderMatches, ScStatus
| order by TimeGenerated desc

Flags inbound HTTP requests to Camel-fronted endpoints that carry gridfs.* headers or MongoDB NoSQL operators ($where, $ne, $gt, $regex) which could override GridFS producer operations or inject query operators against camel-mongodb-gridfs.

critical severity medium confidence

Data Sources

Azure App Service HTTP Logs Web Application Firewall Logs Reverse Proxy Logs

Required Tables

AppServiceHTTPLogs AzureDiagnostics

False Positives

  • Internal automated test suites sending crafted gridfs.* headers during CI integration tests
  • Legitimate GridFS management tooling that intentionally sets gridfs.operation headers
  • Security scanners/pentest tooling probing the same headers as part of authorized assessments

Sigma rule & cross-platform mapping

The detection logic for Apache Camel camel-mongodb-gridfs Header Injection / GridFS Operation Override (CVE-2026-48204) (CVE-2026-48204) above is provided in a vendor-neutral form so you can deploy it on any SIEM. The same logic is shipped here as native KQL (Microsoft Sentinel / Defender), SPL (Splunk), Elastic (Elastic Security (EQL)), QRadar (IBM QRadar (AQL)), Sumo (Sumo Logic CSE), YARA-L (Google Chronicle / SecOps), LogScale (CrowdStrike LogScale (CQL)) queries. In Sigma terms, this detection targets the following logsource:

logsource:
  category: network_connection
  product: windows

Browse the community-maintained Sigma rules for this technique:


Testing Methodology

Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1GridFS Operation Override via Header Injection

    Expected signal: HTTP access log entry showing the gridfs.operation header; MongoDB profiler entry for a delete operation against fs.files/fs.chunks that was not expected for an upload request.

  2. Test 2NoSQL Operator Injection via gridfs.query Header

    Expected signal: HTTP request log with gridfs.query header containing $where; MongoDB profiler log showing a find operation using an unexpected $where clause.

  3. Test 3Bulk GridFS Listing via listAll Override

    Expected signal: HTTP access log entry showing gridfs.operation=listAll on an endpoint intended for scoped reads; MongoDB profiler entry showing a broad find/list query against fs.files.

Unlock playbooks & atomic tests with Pro

Get the full detection package for CVE-2026-48204 — response playbook and atomic red team tests, plus investigation guidance and hunting queries.

df00tech Pro — £29/user/month

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections