Skip to main content

Apache Camel CVE-2026-48204

| EUVDEUVD-2026-41839 CRITICAL
Improper Input Validation (CWE-20)
9.8
CVSS 3.1 · Vendor
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach unauthenticated HTTP consumer
  2. Delivery
    Send request with gridfs.operation header
  3. Exploit
    Header bypasses Camel HTTP filter
  4. Execution
    Override producer operation to remove/listAll/findOne
  5. Persist
    Inject gridfs.metadata as Mongo document
  6. Impact
    Read, 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.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv3 – 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)
v2 Jul 06, 2026 - 21:18 cvss changed CVSS 9.8

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).

v1 Jul 05, 2026 - 20:46

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

Apache Camel 4.0.0 <4.14.8
Apache Camel 4.15.0 <4.18.3
Apache Camel 4.19.0 <4.21.0

Affected Packages

maven org.apache.camel:camel-mongodb-gridfs fix: 4.14.8, 4.18.3, 4.21.0
euvd apache_camel fix: 4.14.8, 4.18.3, 4.21.0

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

Vendor (CNA) PRIMARY 9.8 MEDIUM
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 9.8 CRITICAL

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).

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (CNA).

CVSS VectorVendor

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

4
Analysis Updated
Jul 06, 2026 - 21:19 vuln.today
v3 - CVSS changed
Analysis Updated
Jul 06, 2026 - 21:18 vuln.today
v2 - CVSS changed
CVSS changed
Jul 06, 2026 - 20:22 NVD
9.8 (CRITICAL)
Patch available
Jul 06, 2026 - 10:01 EUVD

Description PRE-NVD

Disclosed via oss-security. NVD scoring and full description are pending.

Executive ViewAI

Why It Matters

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.

Business Impact: Severe
Compensating Controls

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

EPSS Score
0.2%
Top 94% exploitable
Prevalence
High
Apache Camel is a widely deployed enterprise integration framework, though the GridFS component is niche.
Threat Intel
1
1 sources
Social Media
1
Sightings
Data Quality
6 sources
Confidence: High

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.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Out-of-Cycle
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
Very High
Technical Impact
Total

Priority Score

34
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +34
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Malicious file upload attacks exploit insufficient validation when web applications accept user-provided files.

More in Camel

View all
CVE-2025-27636 MEDIUM POC
5.6 Mar 09

Bypass/Injection vulnerability in Apache Camel components under particular conditions.10.0 through <= 4.10.1, from 4.8.0

CVE-2014-0002 HIGH POC
7.5 Mar 21

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

CVE-2016-8749 CRITICAL POC
9.8 Mar 28

Apache Camel's Jackson and JacksonXML unmarshalling operation are vulnerable to Remote Code Execution attacks. Rated cri

CVE-2014-0003 HIGH POC
7.5 Mar 21

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

CVE-2026-23552 CRITICAL POC
9.1 Feb 23

Cross-realm token acceptance bypass in Apache Camel Keycloak security policy. The KeycloakSecurityPolicy fails to proper

CVE-2026-25747 HIGH POC
8.8 Feb 23

Deserialization of Untrusted Data vulnerability in Apache Camel LevelDB component. The Camel-LevelDB DefaultLevelDBSeria

CVE-2026-40473 HIGH POC
8.8 Apr 27

Unsafe Java deserialization in the Apache Camel camel-mina component (versions 3.0.0 through 4.14.5, 4.15.0 through 4.18

CVE-2019-0194 HIGH POC
7.5 Apr 30

Apache Camel's File is vulnerable to directory traversal. Rated high severity (CVSS 7.5), this vulnerability is remotely

CVE-2017-12634 CRITICAL
9.8 Nov 15

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

CVE-2015-5344 CRITICAL
9.8 Feb 03

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

CVE-2017-12633 CRITICAL
9.8 Nov 15

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

CVE-2013-4330 MEDIUM
6.8 Oct 04

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

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy