CVE-2026-49365: Apache Camel sensitive information disclosure in Netty HTTP component

CVE-2026-49365 · Severity: medium · CVSS 5.3 · Published 2026-07-06

Apache Camel's Netty-HTTP server component handles incoming HTTP requests and processes them through integration routes. When errors occur during route processing, the component incorrectly defaults to exposing the full Java stack trace in the HTTP response, which can leak credentials, internal system details, and architecture information. An attacker with network access to the endpoint can intentionally trigger errors (e.g., malformed requests) to extract this sensitive information and plan further attacks on the system.

Technologies: Apache Camel, org.apache.camel:camel-netty-http (Maven). Vendors: Apache, Maven.

Quick answers

Is CVE-2026-49365 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-49365 being exploited in the wild.
How severe is CVE-2026-49365?
Medium severity, with a CVSS score of 5.3, published 6 July 2026.
Which products and versions are affected?
Apache Camel 4.0.0 to 4.14.7, 4.15.0 to 4.18.2, 4.19.0 to 4.20.x; org.apache.camel:camel-netty-http (Maven) ECOSYSTEM:introduced=4.0.0,fixed=4.14.8.
Is there a fix for CVE-2026-49365?
Yes. org.apache.camel:camel-netty-http (Maven): upgrade to 4.14.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-49365 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-49365?
Check whether you run Apache Camel or org.apache.camel:camel-netty-http (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.apache.camel:camel-netty-http (Maven): upgrade to 4.14.8 or later
    # set org.apache.camel:camel-netty-http to 4.14.8 in your pom.xml or build.gradle

Technical details

The vulnerability is an information disclosure issue (CWE-209) in the camel-netty-http HTTP server consumer. The muteException configuration option, which controls whether processing error details are returned to clients, defaults to false due to an uninitialized primitive boolean field—a deviation from other Camel HTTP components (camel-http, camel-jetty, camel-servlet, camel-platform-http) which default it to true. When muteException=false, the DefaultNettyHttpBinding writes the full Throwable stack trace into the HTTP response body as text/plain when an exception occurs during route processing. Any unauthenticated attacker capable of reaching the endpoint can trigger errors via malformed request bodies, invalid parameters, or other route-internal failures to obtain the stack trace. Exposed details include embedded credentials, internal hostnames and IP addresses, filesystem paths, dependency versions, database names, and class structures. The issue affects versions 4.0.0–4.14.7, 4.15.0–4.18.2, and 4.19.0–4.20.x, with patches available in 4.14.8, 4.18.3, and 4.21.0 respectively. Workarounds include setting muteException=true explicitly on affected consumers.

Affected products

  • Apache Camel 4.0.0 to 4.14.7, 4.15.0 to 4.18.2, 4.19.0 to 4.20.x

Identifiers

  • CVE-2026-49365
  • GHSA-42q5-xw42-xf9g

Timeline

  • 2026-07-06: disclosed
  • 2026-07-06: patched: Fixes released in versions 4.14.8, 4.18.3, and 4.21.0

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.