Is CVE-2026-33453 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-33453 being exploited in the wild.

How severe is CVE-2026-33453?

Critical severity, with a CVSS score of 10, published 27 April 2026.

Which products and versions are affected?

org.apache.camel:camel-coap (Maven) ECOSYSTEM:introduced=4.14.0,fixed=4.14.6.

Is there a fix for CVE-2026-33453?

Yes. org.apache.camel:camel-coap (Maven): upgrade to 4.14.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-33453 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-33453?

Check whether you run org.apache.camel:camel-coap (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-33453: Apache Camel remote code execution in camel-coap component

CVE-2026-33453 · Severity: critical · CVSS 10 · Published 2026-04-27

Apache Camel is a popular integration framework used to connect different software applications. A vulnerability in its CoAP component allows an unauthenticated attacker to execute malicious commands on the server by sending a single specially crafted network packet. This could lead to a full system takeover, unauthorized data access, or service disruption.

Vendors: Maven.

Quick answers

Is CVE-2026-33453 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-33453 being exploited in the wild.
How severe is CVE-2026-33453?: Critical severity, with a CVSS score of 10, published 27 April 2026.
Which products and versions are affected?: org.apache.camel:camel-coap (Maven) ECOSYSTEM:introduced=4.14.0,fixed=4.14.6.
Is there a fix for CVE-2026-33453?: Yes. org.apache.camel:camel-coap (Maven): upgrade to 4.14.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-33453 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-33453?: Check whether you run org.apache.camel:camel-coap (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

org.apache.camel:camel-coap (Maven): upgrade to 4.14.6 or later

# set org.apache.camel:camel-coap to 4.14.6 in your pom.xml or build.gradle

Technical details

The camel-coap component in Apache Camel fails to apply a HeaderFilterStrategy when processing incoming CoAP requests. Specifically, CamelCoapResource.handleRequest() maps URI query parameters directly to Camel Exchange headers. An unauthenticated attacker can send a single CoAP UDP packet to inject internal headers (prefixed with 'Camel*'). When these headers are forwarded to sensitive producers like camel-exec, they can override configuration parameters to execute arbitrary OS commands. The vulnerability provides an interactive RCE channel as the command output is returned in the CoAP response. Fixed in versions 4.14.6, 4.18.1, and 4.19.0.

Affected products

Apache Camel 4.14.0 to 4.14.5, 4.15.0 to 4.18.0, 4.19.0

Identifiers

CVE-2026-33453
GHSA-695c-x5gc-94gj

Timeline

2026-04-26: disclosed: Initial disclosure on oss-security mailing list
2026-04-27: advisory: Official Apache Camel security advisory published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.