Skip to main content
VulnerabilityPublished

CVE-2026-56139: Apache Camel Undertow · Generation of Error Message Containing Sensitive Information

Affects Apache Camel UndertowSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium · fixed in 4.21.0 : update Apache Camel Undertow when convenient.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.21.0, 4.18.3, 4.14.8
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade Apache to 4.21.0, 4.18.3 or 4.14.8.

Affected software

ProductAffectedFixed in
Apache Software FoundationApache Camel UndertowAffected
  • >=4.19.0 <4.21.0
Fixed in
  • 4.21.0
Apache Software FoundationApache Camel UndertowAffected
  • >=4.15.0 <4.18.3
Fixed in
  • 4.18.3
Apache Software FoundationApache Camel UndertowAffected
  • >=4.0.0 <4.14.8
Fixed in
  • 4.14.8
MavenApache Software Foundation/org.apache.camel:camel-undertowpkg:maven/Apache Software Foundation/org.apache.camel:camel-undertowOther threatsAffected
  • >=4.0.0 <4.14.8
  • >=4.15.0 <4.18.3
  • >=4.19.0 <4.21.0
Fixed in
  • 4.14.8
  • 4.18.3
  • 4.21.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in Apache Camel Undertow version 4.21.0, and in LTS releases 4.14.8 and 4.18.3. Users are strongly recommended to upgrade to these versions to resolve the issue. For deployments that cannot upgrade immediately, explicitly set the muteException option to true on the camel-undertow consumer (e.g., undertow:http://0.0.0.0:8080/api?muteException=true or globally via camel.component.undertow.mute-exception=true) to prevent stack traces from being returned on processing errors. Note that this workaround does not apply to Rest DSL consumers on affected versions, as they ignore the muteException setting until the fix is applied.

Description

Generation of Error Message Containing Sensitive Information vulnerability in Apache Camel Undertow Component. The camel-undertow HTTP server consumer exposes a muteException option that controls what is returned to the client when a route processing error occurs. This option defaulted to false, whereas the other Camel HTTP server components (camel-http / camel-jetty / camel-servlet and camel-platform-http) default it to true. With muteException=false, when a request triggers an exception during route processing the consumer writes the full Throwable stack trace into the HTTP response body as text/plain instead of returning an empty body. Any unauthenticated client that can reach the endpoint and cause a processing error - for example by sending a malformed request body, an invalid parameter, or otherwise triggering a route-internal failure - therefore receives a complete Java stack trace. Such a stack trace can disclose sensitive internal information, including credentials embedded in exception messages, internal host names and IP addresses, filesystem paths, dependency and version details, database and class names, and the application's internal structure, which an attacker can use to plan further attacks. In addition, for Rest DSL consumers the muteException option was not honoured at all: the RestUndertowHttpBinding was created with a hard-coded false, so the stack trace was returned even when muteException=true had been configured. 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. For deployments that cannot upgrade immediately, set muteException=true explicitly on the camel-undertow consumer (for example undertow: http://0.0.0.0:8080/api?muteException=true , or globally via the camel.component.undertow.mute-exception=true property), so that processing errors no longer return the stack trace to the client; note that on affected releases this workaround does not cover Rest DSL consumers, whose binding ignores the option until the fix is applied.

References

Community reviews

Loading reviews…