dbcve.org
CamelApplication · Apache

CVE-2026-48204

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-06
Fix available
A fix is available. Upgrade to 4.14.8 / 4.18.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Apache Camel mongodb-gridfs component allows attackers to override GridFS operations via HTTP headers (gridfs.operation, gridfs.objectid, etc.) that pass through HttpHeaderFilterStrategy unfiltered because they lack the Camel/camel prefix. This enables unauthorized file deletion, enumeration, reading, and NoSQL operator injection via gridfs.metadata.

MitigationUpgrade to Apache Camel 4.21.0 (or 4.14.8/4.18.3 for LTS streams), and update code to use CamelGridFs* prefixed header constants instead of gridfs.* names; alternatively, set explicit operation on endpoints and strip gridfs.* headers from untrusted ingress.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CamelApplication
Affected:>= 4.0.0, < 4.14.8>= 4.15.0, < 4.18.3>= 4.19.0, < 4.21.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify mongodb-gridfs component usage
    Search codebase for camel-mongodb-gridfs dependency in pom.xml, build.gradle, or equivalent; search for routes using 'mongodb-gridfs' component in XML, Java, or YAML route definitions
    Affected if The camel-mongodb-gridfs component is present in the project dependencies or routes
  2. Check Apache Camel version
    Locate the Camel version from pom.xml, gradle dependencies, or runtime logs; compare against affected ranges: < 4.14.8, 4.15.0 to < 4.18.3, 4.19.0 to < 4.21.0
    Affected if The installed Apache Camel version falls within any of the affected ranges
  3. Inspect HttpHeaderFilterStrategy configuration
    Find the HttpHeaderFilterStrategy bean or configuration in the Camel context; examine the headerFilterStrategy setting for inbound or outbound HTTP endpoints, noting which header prefixes are filtered
    Affected if The filter allows headers without the Camel/camel prefix to pass through to the GridFS endpoint unfiltered
  4. Check for unprefixed gridfs.* header usage
    Search source code for references to header names 'gridfs.operation', 'gridfs.objectid', 'gridfs.filename', 'gridfs.metadata', or similar unprefixed patterns in route definitions, processors, or header manipulations
    Affected if Code references or accepts unprefixed gridfs.* headers that could be injected from external HTTP requests
  5. Verify endpoint exposure to untrusted input
    Determine if a REST DSL, servlet, or other HTTP ingress exposes the GridFS route directly; examine if incoming HTTP request headers are passed to the GridFS consumer without stripping or validating gridfs.* headers
    Affected if The GridFS endpoint is accessible via HTTP and headers from untrusted sources can reach it

A user is affected if they run a vulnerable Camel version with the mongodb-gridfs component exposed to untrusted HTTP input that allows unprefixed gridfs.* headers to pass through to GridFS operations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.14.8 / 4.18.3 / 4.21.0 or later
Fixed in 4.14.84.18.34.21.0
Interim mitigation

Upgrade to Apache Camel 4.21.0 (or 4.14.8/4.18.3 for LTS streams), and update code to use CamelGridFs* prefixed header constants instead of gridfs.* names; alternatively, set explicit operation on endpoints and strip gridfs.* headers from untrusted ingress.

Recommended fix High confidence

4.21.0 (or 4.14.8 for 4.14.x LTS, or 4.18.3 for 4.18.x)

  1. Upgrade Apache Camel to version 4.21.0 (or to 4.14.8 if on the 4.14.x LTS stream, or to 4.18.3 if on the 4.18.x stream)
  2. After upgrading, update any routes that reference the raw header names (gridfs.operation, gridfs.objectid, gridfs.metadata, gridfs.chunksize, gridfs.fileid) to use the new Camel-prefixed constants: CamelGridFsOperation, CamelGridFsObjectId, CamelGridFsMetadata, CamelGridFsChunkSize, CamelGridFsFileId
  3. If immediate upgrade is not possible, mitigate by setting an explicit operation parameter on the mongodb-gridfs: endpoint to prevent operation selection from headers, and configure a filter to strip gridfs.* headers from untrusted ingress HTTP requests before they reach the Camel Exchange
Caveat Routes that drive GridFS operations via raw header names (gridfs.*) must be updated to use the new Camel-prefixed constants (CamelGridFsOperation etc.) after upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Camel Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-48204 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-48204 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data