GHSA-f7g3-2cg6-f5hj
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach unauthenticated HTTP consumer
-
DeliverySend request with gridfs.operation header
-
ExploitHeader bypasses Camel HTTP filter
-
ExecutionOverride producer operation to remove/listAll/findOne
-
PersistInject gridfs.metadata as Mongo document
-
ImpactRead, delete, or enumerate GridFS bucket
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Input validation, allowlisting
|
| Exploitation Conditions | Exploitation requires a Camel route that bridges an HTTP-facing consumer (e.g. platform-http, camel-jetty, servlet) into a mongodb-gridfs: producer where the endpoint's operation parameter is NOT set - which is the default, so the producer reads its operation from the gridfs.operation header. The attacker must be able to reach that HTTP consumer and set arbitrary request headers; no credentials are needed only when that bridging consumer is itself unauthenticated. Limiting factors that reduce real-world risk: the mongodb-gridfs component must actually be in use, the producer's operation must be left unset, and the HTTP ingress must be untrusted/unauthenticated and not already stripping gridfs.* headers - if an explicit operation is configured, or the ingress requires auth or filters these headers, the override cannot occur. |
| Impact | Signals conflict and must be weighed together. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N, C:H/I:H/A:H = 9.8) and the SSVC assessment (automatable: yes, technical impact: total) argue for high priority: where a vulnerable route exists, exploitation is network-based, needs no credentials, and yields read, delete and enumeration of the GridFS bucket plus NoSQL operator injection. Against that, EPSS is only 0.16% (6th percentile), SSVC exploitation status is 'none', and no public exploit or KEV listing exists - consistent with the fact that exploitation is not against a bare default install but requires a specific deployment pattern (an unauthenticated HTTP consumer bridged into a mongodb-gridfs producer with no explicit operation). The 9.8 base score does not capture this configuration dependency, so real-world exposure is narrower than the number implies: treat it as high priority for shops running Camel HTTP-to-GridFS routes, and lower for those who do not use that component or who pin the operation. No conflict exists between the CVSS network vector and the description - both agree on remote, unauthenticated access given the bridging route. |
| Exploit ScenarioDerived | An application exposes a platform-http endpoint that forwards uploads into a mongodb-gridfs: producer with no operation set. An unauthenticated attacker sends an HTTP request carrying gridfs.operation: remove and gridfs.objectid: <target> to delete an arbitrary stored file, or gridfs.operation: listAll to enumerate the entire bucket, and can supply a crafted gridfs.metadata value to inject MongoDB operators. No public POC is currently identified, but the attack is simple to script given AV:N/AC:L/PR:N. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv3 – Jul 06, 2026
Unauthenticated NoSQL operation hijacking in Apache Camel's camel-mongodb-gridfs component (4.0.0-4.14.7, 4.15.0-4.18.2, 4.19.0-4.20.x) lets a remote HTTP client override the intended GridFS operation and inject MongoDB query documents. When a route bridges an HTTP consumer such as platform-http into a mongodb-gridfs: producer that has no explicit operation set (the default), the raw gridfs.operation, gridfs.objectid and gridfs.metadata headers pass through the HTTP header filter because they lack the Camel/camel prefix, allowing an attacker to turn an intended upload into remove, listAll, or findOne and to inject NoSQL operators. There is no public exploit identified at time of analysis and EPSS is low (0.16%), but CVSS is 9.8 and SSVC rates technical impact as total and automatable.
Earlier versions of this analysis (2)
Unauthenticated NoSQL operator injection and unintended file operations affect Apache Camel's camel-mongodb-gridfs component (4.0.0-4.14.7, 4.15.0-4.18.2, 4.19.0-4.20.x) in routes that bridge an HTTP consumer into a mongodb-gridfs producer without an explicit operation. Because the control headers used the non-prefixed names gridfs.operation/gridfs.objectid/gridfs.metadata, HttpHeaderFilterStrategy did not strip them at the HTTP boundary, so any client can override the intended GridFS operation (e.g. flip an upload into remove, listAll or findOne) and inject a crafted MongoDB metadata document. CVSS is 9.8 and SSVC technical impact is 'total', but there is no public exploit identified at time of analysis and EPSS is only 0.16% (6th percentile).
The camel-mongodb-gridfs component in Apache Camel 4.0.0 through 4.20.x exposes routes bridging HTTP to GridFS to full operation override by any HTTP client, because the gridfs.* Exchange header constants lacked the Camel-prefix required for HttpHeaderFilterStrategy to block them at the HTTP boundary. In the default endpoint configuration - where no explicit operation is set - an attacker can switch a file-upload route to remove (targeted file deletion), listAll (full bucket enumeration), or findOne (arbitrary file read), and additionally inject NoSQL operators via the gridfs.metadata header. No public exploit has been identified at time of analysis, but exploitation requires only standard HTTP header manipulation wherever the vulnerable route pattern is deployed.
RemediationAI
Vendor-released patch: upgrade to Apache Camel 4.21.0, which fixes the issue; on the 4.14.x LTS stream upgrade to 4.14.8, and on the 4.18.x stream upgrade to 4.18.3, per https://camel.apache.org/security/CVE-2026-48204.html. After upgrading, any route that drives GridFS operations or metadata through the raw header names must be updated to use the new prefixed constants CamelGridFsOperation, CamelGridFsObjectId, CamelGridFsMetadata, CamelGridFsChunkSize and CamelGridFsFileId instead of the gridfs.* names, or those operations will stop working. For deployments that cannot upgrade immediately, set an explicit operation parameter on the mongodb-gridfs: endpoint so the operation is never taken from a header, and strip all gridfs.* headers from untrusted ingress before the producer (for example with a removeHeaders step on the inbound HTTP route); the trade-off is that legitimate clients relying on header-driven operation selection must be reworked, and the header-stripping filter must be kept in sync with the full set of gridfs.* control headers.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in maven, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Apache Camel is a widely used Java enterprise-integration framework whose routes move messages between components via an Exchange carrying headers. The camel-mongodb-gridfs producer talks to MongoDB GridFS, a specification for storing large binary files as chunked documents in a MongoDB bucket. The producer chooses its action from the gridfs.operation Exchange header whenever the endpoint's operation parameter is unset. The root cause (CWE-20, Improper Input Validation, combined with improper access control) is that the control-header constants were defined as the bare strings gridfs.operation, gridfs.objectid, gridfs.metadata, gridfs.chunksize and gridfs.fileid. HttpHeaderFilterStrategy only strips headers in the Camel/camel namespace at the HTTP boundary, so these un-prefixed control headers were never filtered out and flowed from an inbound HTTP request directly into the Exchange, letting untrusted input drive privileged data-layer operations and be parsed as a MongoDB document.
Know when Camel gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Given the default header-driven route bridged from unauthenticated HTTP, exploitation is network-based with no auth or interaction (AV:N/AC:L/PR:N/UI:N) and yields full read/delete/enumerate impact (C/I/A:H).
Primary rating from Vendor (CNA).
CVSS VectorVendor
Lifecycle Timeline
4Description PRE-NVD
Blast Radius
ecosystem impact- 7 maven packages depend on org.apache.camel:camel-mongodb-gridfs (3 direct, 4 indirect)
Ecosystem-wide dependent count for version 4.0.0.
Articles & Coverage 4
Executive ViewAI
Apache Camel's file management component contains a critical vulnerability that allows remote attackers without credentials to intercept and override file operations, potentially enabling data deletion, corruption, or exfiltration. This affects organizations using Apache Camel versions 4.0.0 through 4.20.x that expose file management services to the network. No public exploit identified at time of analysis, but a vendor patch is available and should be deployed immediately.
Apply vendor patch. Until patching is complete: restrict network access to file management endpoints to trusted sources only, enable logging and alerts for suspicious header patterns related to file operations, and ensure all routes have explicit operation definitions configured.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Malicious file upload attacks exploit insufficient validation when web applications accept user-provided files.
Bypass/Injection vulnerability in Apache Camel components under particular conditions.10.0 through <= 4.10.1, from 4.8.0
The XSLT component in Apache Camel before 2.11.4 and 2.12.x before 2.12.3 allows remote attackers to read arbitrary file
Apache Camel's Jackson and JacksonXML unmarshalling operation are vulnerable to Remote Code Execution attacks. Rated cri
The XSLT component in Apache Camel 2.11.x before 2.11.4, 2.12.x before 2.12.3, and possibly earlier versions allows remo
Cross-realm token acceptance bypass in Apache Camel Keycloak security policy. The KeycloakSecurityPolicy fails to proper
Deserialization of Untrusted Data vulnerability in Apache Camel LevelDB component. The Camel-LevelDB DefaultLevelDBSeria
Unsafe Java deserialization in the Apache Camel camel-mina component (versions 3.0.0 through 4.14.5, 4.15.0 through 4.18
Apache Camel's File is vulnerable to directory traversal. Rated high severity (CVSS 7.5), this vulnerability is remotely
The camel-castor component in Apache Camel 2.x before 2.19.4 and 2.20.x before 2.20.1 is vulnerable to Java object de-se
The camel-xstream component in Apache Camel before 2.15.5 and 2.16.x before 2.16.1 allow remote attackers to execute arb
The camel-hessian component in Apache Camel 2.x before 2.19.4 and 2.20.x before 2.20.1 is vulnerable to Java object de-s
Apache Camel before 2.9.7, 2.10.0 before 2.10.7, 2.11.0 before 2.11.2, and 2.12.0 allows remote attackers to execute arb
EUVD-2026-41839
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB