CVE-2026-49365
Received Received - Intake

Information Disclosure in Apache Camel Netty HTTP

Publication date: 2026-07-06

Last updated on: 2026-07-06

Assigner: Apache Software Foundation

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 Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-06
Last Modified
2026-07-06
Generated
2026-07-06
AI Q&A
2026-07-06
EPSS Evaluated
N/A
NVD
CVE-2026-49365
EUVD
EUVD-2026-41846

Affected Vendors & Products

Showing 6 associated CPEs
Vendor Product Version / Range
apache camel to 4.14.8 (exc)
apache camel to 4.18.3 (exc)
apache camel to 4.21.0 (exc)
apache camel 4.14.8
apache camel 4.18.3
apache camel 4.21.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-209 The product generates an error message that includes sensitive information about its environment, users, or associated data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-49365 is a medium-severity vulnerability in Apache Camel's camel-netty-http component. The issue occurs because the muteException option defaults to false, causing the HTTP server to return full Java stack traces in error responses when processing errors happen.

This behavior exposes sensitive internal information such as credentials, hostnames, IP addresses, filesystem paths, dependency and version details, database and class names, and the application's internal structure to any unauthenticated client that can trigger a route failure.

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. It was fixed by changing the default of muteException to true, which prevents stack traces from being returned in error responses.

Impact Analysis

This vulnerability can impact you by exposing sensitive internal information to unauthenticated clients who can trigger errors on your HTTP endpoints.

Exposed information may include credentials, internal hostnames and IP addresses, filesystem paths, dependency and version details, database and class names, and the internal structure of your application.

Attackers can use this information to plan further attacks against your system, increasing the risk of unauthorized access or exploitation.

Detection Guidance

This vulnerability can be detected by sending requests that trigger processing errors to the camel-netty-http HTTP server consumer endpoint and observing the HTTP response.

If the server returns a full Java stack trace in the HTTP response body (text/plain) when an error occurs, it indicates that the muteException option is set to false or not set, and the system is vulnerable.

A simple detection command could be a curl request with malformed data or invalid parameters to the affected endpoint, for example:

  • curl -v -X POST http://your-server:8080/api -d 'malformed_data'

If the response contains a Java stack trace, the vulnerability is present.

Mitigation Strategies

The immediate mitigation steps are to upgrade Apache Camel to a fixed version or configure the muteException option to true.

  • Upgrade to Apache Camel version 4.21.0 or later.
  • If using the 4.14.x LTS release stream, upgrade to version 4.14.8 or later.
  • If using the 4.18.x release stream, upgrade to version 4.18.3 or later.

If upgrading immediately is not possible, explicitly set the muteException option to true on the camel-netty-http consumer to prevent stack traces from being returned in error responses.

  • Set muteException=true in the endpoint URI, for example: netty-http:http://0.0.0.0:8080/api?muteException=true
  • Or set it globally via the property: camel.component.netty-http.configuration.mute-exception=true

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-49365. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart