dbcve.org
CamelApplication · Apache

CVE-2026-33453

CRITICAL · 10.0 CVSS v3.1 Published 2026-04-27
Fix available
A fix is available. Upgrade to after 4.14.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Improperly Controlled Modification of Dynamically-Determined Object Attributes vulnerability in Apache Camel Camel-Coap component. Apache Camel's camel-coap component is vulnerable to Camel message header injection, leading to remote code execution when routes forward CoAP requests to header-sensitive producers (e.g. camel-exec) The camel-coap component maps incoming CoAP request URI query parameters directly into Camel Exchange In message headers without applying any HeaderFilterStrategy.   Specifically, CamelCoapResource.handleRequest() iterates over OptionSet.getUriQuery() and calls camelExchange.getIn().setHeader(...) for every query parameter. CoAPEndpoint extends DefaultEndpoint rather than DefaultHeaderFilterStrategyEndpoint, and CoAPComponent does not implement HeaderFilterStrategyComponent; the component contains no references to HeaderFilterStrategy at all. As a result, an unauthenticated attacker who can send a single CoAP UDP packet to a Camel route consuming from coap:// can inject arbitrary Camel internal headers (those prefixed with Camel*) into the Exchange. When the route delivers the message to a header-sensitive producer such as camel-exec, camel-sql, camel-bean, camel-file, or template components (camel-freemarker, camel-velocity), the injected headers can alter the producer's behavior. In the case of camel-exec, the CamelExecCommandExecutable and CamelExecCommandArgs headers override the executable and arguments configured on the endpoint, resulting in arbitrary OS command execution under the privileges of the Camel process. The producer's output is written back to the Exchange body and returned in the CoAP response payload by CamelCoapResource, giving the attacker an interactive RCE channel without any need for out-of-band exfiltration.                                                                                                                                                                         Exploitation prerequisites are minimal: a single unauthenticated UDP datagram to the CoAP port (default 5683). CoAP (RFC 7252) has no built-in authentication, and DTLS is optional and disabled by default. Because the protocol is UDP-based, HTTP-layer WAF/IDS controls do not apply. This issue affects Apache Camel: from 4.14.0 through 4.14.5, from 4.18.0 before 4.18.1, 4.19.0. Users are recommended to upgrade to version 4.18.1 or 4.19.0, fixing the issue.

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 camel-coap component in Apache Camel lacks HeaderFilterStrategy, causing incoming CoAP URI query parameters to be directly mapped into Camel Exchange headers without filtering. This allows unauthenticated attackers sending a single UDP packet to inject arbitrary Camel* internal headers (like CamelExecCommandExecutable) that can override producer configurations, enabling RCE when routes use header-sensitive producers like camel-exec.

MitigationUpgrade Apache Camel to version 4.18.1 or 4.19.0, which implements proper HeaderFilterStrategy to filter out internal headers from query parameters.

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.14.0, <= 4.14.5= 4.18.0= 4.19.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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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. Check Apache Camel version
    Run 'camel --version' or inspect the camel-core JAR manifest, or check your dependency management for the Apache Camel version
    Affected if Version is 4.14.0, 4.14.1, 4.14.2, 4.14.3, 4.14.4, 4.14.5, 4.18.0, or 4.19.0
  2. Identify if camel-coap component is deployed
    Search for camel-coap JAR in your classpath or dependencies, or look for 'coap:' endpoints in your route definitions
    Affected if The camel-coap component is present in the runtime
  3. Inspect routes for coap: endpoint usage
    Review Camel route XML/Java DSL files and search for endpoints starting with 'coap:' or 'coaps:'
    Affected if Routes contain coap: or coaps: consumer endpoints that accept query parameters
  4. Check for forwarding to header-sensitive producers
    Examine route definitions to see if messages from coap: endpoints are sent to producers like camel-exec, camel-velocity, or other components that process sensitive headers
    Affected if Routes forward CoAP messages to producers that interpret headers as commands or configuration (such as camel-exec) without an intervening HeaderFilterStrategy
  5. Verify HeaderFilterStrategy is applied to CoAP endpoints
    Inspect route configurations for HeaderFilterStrategy applied to the CoAP endpoint or a containing route, or check if a global HeaderFilterStrategy is configured that filters Camel* headers
    Affected if No HeaderFilterStrategy is applied to filter out internal Camel* headers before query parameters are mapped to exchange headers

You are affected if running a vulnerable Apache Camel version (4.14.0-4.14.5, 4.18.0, or 4.19.0) with the camel-coap component active in routes that forward to header-sensitive producers without proper HeaderFilterStrategy filtering.

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 a release after 4.14.5
Interim mitigation

Upgrade Apache Camel to version 4.18.1 or 4.19.0, which implements proper HeaderFilterStrategy to filter out internal headers from query parameters.

Recommended fix High confidence

4.18.1 or 4.19.0

  1. Identify the current Apache Camel version in use by checking project dependencies or build configuration
  2. Stop all Camel applications and services using the vulnerable camel-coap component
  3. Update the Camel version in your project's dependency management (e.g., Maven pom.xml, Gradle build file) to version 4.18.1 or 4.19.0
  4. Run dependency resolution to ensure the updated camel-coap artifact (and related Camel modules) are pulled at the correct version
  5. Rebuild and recompile the project to incorporate the fixed camel-coap component
  6. Test the application to verify the CoAP endpoint functions correctly with the fixed component
  7. Restart the Camel application and verify the CoAP service is operational on port 5683 (or configured port)
Caveat Minor version upgrades may include API changes; review release notes for any breaking changes between your current version and the target version

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

Fix this in Camel Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33453 — 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-33453 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