CVE-2026-56139: Apache Camel Undertow: The muteException consumer option defaulted to false, so a processing error returned the full Java stack trace in the HTTP response body, disclosing sensitive internal information to unauthenticated clients

Published Jul 5, 2026
·
Updated

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.

Affected Software

4 affected components
Apache Camel>=4.0.0<4.14.8, >=4.15.0<4.18.3, >=4.19.0<4.21.0
Apache Camel>=4.0.0<4.14.8
Apache Camel>=4.15.0<4.18.3
Apache Camel>=4.19.0<4.21.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Apache Camel to a version that resolves this vulnerability.

    Fixed in 4.21.0
  2. Upgrade

    Upgrade Apache Camel 4.14.x LTS to a version that resolves this vulnerability.

    Fixed in 4.14.8
  3. Upgrade

    Upgrade Apache Camel 4.18.x to a version that resolves this vulnerability.

    Fixed in 4.18.3
  4. Configuration

    For deployments that cannot upgrade immediately, set muteException=true explicitly on the camel-undertow consumer (e.g., undertow:http://0.0.0.0:8080/api?muteException=true) so processing errors no longer return the Java stack trace to unauthenticated clients.

    Apache Camel Undertow (camel-undertow) HTTP server consumer muteException = true
  5. Configuration

    Alternatively, configure muteException globally via the property camel.component.undertow.mute-exception=true so that the camel-undertow consumer stops returning stack traces in HTTP response bodies on route processing errors.

    Apache Camel Undertow (camel-undertow) HTTP server consumer camel.component.undertow.mute-exception = true
  6. Configuration

    Note that on affected releases the Rest DSL consumer does not honour muteException because RestUndertowHttpBinding is created with a hard-coded false; apply the fix via upgrade to address this case.

    Apache Camel Undertow Rest DSL consumers (RestUndertowHttpBinding) muteException = ignored_on_affected_releases
  7. Compensating control

    For deployments temporarily unable to upgrade, treat any exposed endpoints as sensitive: restrict/unexpose the Camel Undertow HTTP endpoints to reduce unauthenticated reachability while the muteException workaround/upgrade is applied.

Event History

Jul 6, 2026
CVE Published
via MITRE·08:15 AM
Data Sourced
via MITRE·08:15 AM
DescriptionWeakness
Data Sourced
via NVD·09:16 AM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-56139?

CVE-2026-56139 has a risk rating of 30, indicating it is a significant security vulnerability.

2

How do I fix CVE-2026-56139?

To fix CVE-2026-56139, set the muteException option to true in the Apache Camel Undertow configuration.

3

What information is disclosed in CVE-2026-56139?

CVE-2026-56139 can disclose sensitive internal information, including full Java stack traces, to unauthenticated clients.

4

What component is affected by CVE-2026-56139?

CVE-2026-56139 affects the Apache Camel Undertow component.

5

When was CVE-2026-56139 published?

CVE-2026-56139 was published on July 5, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203