CVE-2026-49365: CWE-209 Generation of Error Message Containing Sensitive Information in Apache Software Foundation Apache Camel
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.
AI Analysis
Technical Summary
The camel-netty-http HTTP server consumer in Apache Camel exposes a vulnerability (CWE-209) where the muteException option defaults to false, causing full Throwable stack traces to be returned in HTTP response bodies when route processing errors occur. This can disclose sensitive internal information such as credentials, hostnames, IP addresses, filesystem paths, and application structure to unauthenticated clients. The vulnerability affects Apache Camel versions from 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, and from 4.19.0 before 4.21.0. The issue is fixed in versions 4.14.8, 4.18.3, and 4.21.0 respectively.
Potential Impact
An attacker able to send requests that trigger processing errors on the vulnerable camel-netty-http endpoint can receive detailed Java stack traces in HTTP responses. These stack traces may contain sensitive information such as embedded credentials, internal hostnames and IP addresses, filesystem paths, dependency and version details, database and class names, and internal application structure. This information disclosure can aid attackers in planning further attacks.
Mitigation Recommendations
Users should upgrade to Apache Camel versions 4.14.8, 4.18.3, or 4.21.0 depending on their release stream to fix this vulnerability. For deployments unable to upgrade immediately, explicitly set the muteException option to true on the camel-netty-http consumer (e.g., netty-http:http://0.0.0.0:8080/api?muteException=true or globally via camel.component.netty-http.configuration.mute-exception=true) to prevent stack traces from being returned in HTTP responses.
CVE-2026-49365: CWE-209 Generation of Error Message Containing Sensitive Information in Apache Software Foundation Apache Camel
Description
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.
CVSS v3.1
Score 5.3medium
Affected software
pkg:maven/Apache Software Foundation/org.apache.camel:camel-netty-httpRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The camel-netty-http HTTP server consumer in Apache Camel exposes a vulnerability (CWE-209) where the muteException option defaults to false, causing full Throwable stack traces to be returned in HTTP response bodies when route processing errors occur. This can disclose sensitive internal information such as credentials, hostnames, IP addresses, filesystem paths, and application structure to unauthenticated clients. The vulnerability affects Apache Camel versions from 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, and from 4.19.0 before 4.21.0. The issue is fixed in versions 4.14.8, 4.18.3, and 4.21.0 respectively.
Potential Impact
An attacker able to send requests that trigger processing errors on the vulnerable camel-netty-http endpoint can receive detailed Java stack traces in HTTP responses. These stack traces may contain sensitive information such as embedded credentials, internal hostnames and IP addresses, filesystem paths, dependency and version details, database and class names, and internal application structure. This information disclosure can aid attackers in planning further attacks.
Mitigation Recommendations
Users should upgrade to Apache Camel versions 4.14.8, 4.18.3, or 4.21.0 depending on their release stream to fix this vulnerability. For deployments unable to upgrade immediately, explicitly set the muteException option to true on the camel-netty-http consumer (e.g., netty-http:http://0.0.0.0:8080/api?muteException=true or globally via camel.component.netty-http.configuration.mute-exception=true) to prevent stack traces from being returned in HTTP responses.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- apache
- Date Reserved
- 2026-05-29T16:50:08.917Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a4b6cb027e9c79719252692
Added to database: 07/06/2026, 08:52:00 UTC
Last enriched: 07/14/2026, 09:09:19 UTC
Last updated: 08/18/2026, 10:54:24 UTC
Views: 62
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.