EUVD-2026-41846
GHSA-42q5-xw42-xf9g
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Network-reachable endpoint, no auth required, no user interaction; confidentiality rated Low rather than High because disclosure is conditional on exception verbosity and what credentials appear in stack traces.
Primary rating from Vendor (CNA).
CVSS VectorVendor
Lifecycle Timeline
3Blast Radius
ecosystem impact- 13 maven packages depend on org.apache.camel:camel-netty-http (5 direct, 8 indirect)
Ecosystem-wide dependent count for version 4.0.0.
Description PRE-NVD
Articles & Coverage 5
AnalysisAI
Stack trace disclosure in Apache Camel's camel-netty-http component (versions 4.0.0-4.21.0 across three release streams) exposes full Java Throwable stack traces to unauthenticated HTTP clients whenever a route processing error occurs under the default configuration. The root cause is an insecure default: the muteException option backed by an uninitialized Java primitive boolean defaulted to false in camel-netty-http while all other Camel HTTP server components (camel-http, camel-jetty, camel-servlet, camel-platform-http) correctly default it to true. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog, but the low-effort triggering condition - any malformed request that causes a route exception - makes opportunistic enumeration straightforward against exposed endpoints.
Technical ContextAI
Apache Camel is an open-source Java integration framework implementing Enterprise Integration Patterns; the camel-netty-http component provides an HTTP server consumer built on the Netty async networking library. The affected artifact is org.apache.camel:camel-netty-http. The root cause is classified as CWE-209 (Generation of Error Message Containing Sensitive Information): the muteException field in the Netty HTTP consumer was an uninitialized Java primitive boolean, which the JVM initializes to false by default. The DefaultNettyHttpBinding class serializes the full java.lang.Throwable stack trace into the HTTP response body as text/plain when muteException is false. This contrasts with other Camel HTTP consumers that explicitly initialize the same field to true. No CPE string was provided by NVD at time of analysis; the affected artifact can be identified via Maven coordinates org.apache.camel:camel-netty-http within the three affected version ranges. The fix (GitHub PR #23913, commit 6cea553) aligns the default to true at both component and endpoint levels, with backports to the 4.18.x and 4.14.x LTS streams.
RemediationAI
The primary fix is to upgrade to Apache Camel 4.14.8 (for users on the 4.14.x LTS stream), 4.18.3 (for users on the 4.18.x stream), or 4.21.0 (current), all of which flip the muteException default to true at both component and endpoint levels. Upgrade guidance and release notes are available at https://camel.apache.org/security/CVE-2026-49365.html. For deployments that cannot immediately upgrade, the vendor-recommended workaround is to explicitly set muteException=true on the camel-netty-http consumer: either via the endpoint URI parameter (e.g., netty-http:http://0.0.0.0:8080/api?muteException=true) or globally via the application property camel.component.netty-http.configuration.mute-exception=true. Note that enabling muteException takes precedence over the transferException option - routes that previously relied on transferException=true to pass exception objects back to callers over camel-netty-http will receive empty response bodies instead and must now explicitly set muteException=false if that behavior is required (documented as a potential breaking change in the 4.21 upgrade guide). As an additional compensating control, restrict network access to camel-netty-http endpoints to trusted internal networks or authenticated proxies, which reduces the exposure window even if muteException remains false.
Oracle Java SE 7 Update 6 and earlier contains multiple sandbox bypass vulnerabilities via the ClassFinder and forName m
Remote code execution in IBM Sterling B2B Integrator, Sterling Integrator, and Tivoli Common Reporting allows unauthenti
Java Runtime Environment sandbox bypass via incorrect image channel verification in 2D component allows remote unauthent
Oracle Java SE JDK/JRE 7 and 6 Update 27 and earlier allows remote code execution with complete system compromise throug
JBoss Seam 2 in Red Hat JBoss EAP 4.3.0 fails to sanitize JBoss Expression Language inputs, allowing remote attackers to
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 update 4 and earlier, 6 up
Multiple vulnerabilities in Oracle Java 7 before Update 11 allow remote attackers to execute arbitrary code by (1) using
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 2 and earlier, 6 Up
The WLS Security component in Oracle WebLogic Server 10.3.6.0, 12.1.2.0, 12.1.3.0, and 12.2.1.0 allows remote attackers
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 7 and earlier allow
Remote unauthenticated attackers can execute arbitrary code on Adobe ColdFusion servers through Java deserialization fla
The ExceptionDelegator component in Apache Struts before 2.2.3.1 interprets parameter values as OGNL expressions during
Same weakness CWE-209 – Error Message Information Leak
View allSame technique Information Disclosure
View allVendor StatusVendor
Share
External POC / Exploit Code
Leaving vuln.today