CVE-2026-49365: Apache Camel: Camel-Netty-HTTP: 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
Generation of Error Message Containing Sensitive Information vulnerability in Apache Camel Netty HTTP component.
The camel-netty-http 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 because the backing field was an uninitialised primitive boolean (Java's default of 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 (via DefaultNettyHttpBinding) 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. 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-netty-http consumer (for example netty-http: http://0.0.0.0:8080/api?muteException=true , or globally via the camel.component.netty-http.configuration.mute-exception=true property), so that processing errors no longer return the stack trace to the client.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Apache Camel (Camel-Netty-HTTP)to a version that resolves this vulnerability.Fixed in 4.14.8 - Upgrade
Upgrade
Apache Camel (Camel-Netty-HTTP)to a version that resolves this vulnerability.Fixed in 4.18.3 - Upgrade
Upgrade
Apache Camel (Camel-Netty-HTTP)to a version that resolves this vulnerability.Fixed in 4.21.0 - Configuration
For deployments that cannot upgrade immediately, set muteException=true explicitly on the camel-netty-http consumer so processing errors no longer return the Java stack trace to unauthenticated clients (example: netty-http: http://0.0.0.0:8080/api?muteException=true).
Camel-Netty-HTTP consumer (netty-http) muteException = true - Configuration
Alternatively, configure muteException globally via camel.component.netty-http.configuration.mute-exception=true so Camel-Netty-HTTP consumer route-processing errors no longer return the stack trace.
Camel (global configuration for camel-netty-http) camel.component.netty-http.configuration.mute-exception = true
Event History
Frequently Asked Questions
What is the severity of CVE-2026-49365?
The severity of CVE-2026-49365 is rated at 30.
How do I fix CVE-2026-49365?
To fix CVE-2026-49365, set the muteException consumer option to true in your Apache Camel Netty HTTP configuration.
What information is leaked in CVE-2026-49365?
CVE-2026-49365 may expose sensitive internal information, including the full Java stack trace, to unauthenticated clients.
Which Apache Camel component is affected by CVE-2026-49365?
CVE-2026-49365 affects the Apache Camel Netty HTTP component.
When was CVE-2026-49365 published?
CVE-2026-49365 was published on July 5, 2026.