Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-84180 Overview
CVE-2026-84180 is an information disclosure vulnerability in the Apache Camel Knative HTTP consumer component. When exchange processing fails on the consumer side, the component writes the raw exception back to the remote caller as the HTTP response body. The returned content includes the exception class name, message, and full stack trace. An unauthenticated external sender can trigger a failure and read internal deployment detail, including class and package names, file system paths, host names, and in some cases configuration or connection strings embedded in exception messages. The flaw is tracked as [CWE-209] Generation of Error Message Containing Sensitive Information.
Critical Impact
Unauthenticated remote callers can harvest internal deployment detail and route topology from exception responses, enabling targeted follow-on attacks against affected Apache Camel services.
Affected Products
- Apache Camel versions 4.0.0 through 4.18.4 (fixed in 4.18.5)
- Apache Camel versions 4.19.0 through 4.22.0 (fixed in 4.22.1)
- Apache Camel mainline versions prior to 4.23.0
Discovery Timeline
- 2026-10-19 - CVE-2026-84180 published to the National Vulnerability Database (NVD)
- 2026-10-19 - Last updated in the NVD database
Technical Details for CVE-2026-84180
Vulnerability Analysis
The camel-knative component exposes an HTTP consumer that handles inbound Knative events. When an exchange fails during processing, the consumer serialises the raised exception directly into the response body returned to the caller. The response therefore carries the fully qualified exception class, the exception message string, and the Java stack trace frames describing the processing route.
This class of information leak gives an attacker several concrete artefacts. Package names and class hierarchies reveal which Camel components and third-party libraries are deployed. Stack frame file names expose source layout and sometimes container paths. Exception messages frequently embed values that the application passed to a failing API, including database URLs, broker endpoints, credentials captured from configuration, or hostnames of internal services.
Root Cause
The Apache Camel project previously introduced a muteException option across its HTTP-family consumers under CAMEL-23651 to suppress exception propagation into HTTP responses. The Knative consumer was not aligned with that behaviour and continued to write exceptions back to the caller by default. The root cause is therefore a missing default-deny on exception serialisation at the HTTP boundary.
Attack Vector
Exploitation requires only network reachability to a Knative-exposed Camel route. No authentication or user interaction is required. The attacker submits malformed input, unexpected content types, invalid headers, or payloads known to trip downstream integrations, and reads the resulting error response body. The returned stack trace and message content are then used to map internal services and craft follow-on requests. See the Apache Camel CVE-2026-84180 Advisory for the vendor description of the attack path.
Detection Methods for CVE-2026-84180
Indicators of Compromise
- HTTP response bodies returned from Knative consumer endpoints that contain Java stack trace fragments, class names such as org.apache.camel.*, or at ...(SourceFile.java:NN) frame patterns.
- Repeated 4xx or 5xx responses from the same remote source paired with crafted or malformed request bodies targeting Knative routes.
- Outbound reconnaissance activity, including targeted probes against internal hostnames or endpoints that first appeared in a prior Camel error response.
Detection Strategies
- Inspect HTTP egress from Camel services via a reverse proxy or service mesh and alert when response bodies match stack trace signatures.
- Correlate web application firewall (WAF) logs for input patterns that reliably trigger 500-class responses from Knative paths.
- Review Camel application logs for Exchange failed events on Knative consumer routes and compare their frequency against baseline.
Monitoring Recommendations
- Enable structured access logging on all Knative-fronted Camel routes and ship logs to a centralised analytics backend for pattern detection.
- Track the Camel runtime version per deployment and alert when hosts remain below 4.18.5, 4.22.1, or 4.23.0.
- Monitor for unusual response body sizes on error paths, which often indicate serialised exceptions rather than normal error envelopes.
How to Mitigate CVE-2026-84180
Immediate Actions Required
- Upgrade Apache Camel to 4.23.0 on mainline deployments.
- Upgrade to 4.18.5 on the 4.18.x LTS stream or 4.22.1 on the 4.22.x LTS stream.
- Audit existing routes for explicit muteException=false settings and remove them unless an operational reason exists.
- Review historical error responses from Knative endpoints to confirm whether sensitive values such as connection strings were previously disclosed.
Patch Information
The fix aligns camel-knative with the behaviour established by CAMEL-23651. The consumer now honours a muteException option that defaults to true, so a route failure returns an empty body with the error status rather than the exception. Setting muteException=false restores the previous output for deployments that depend on it. Patch details are available in GitHub Pull Request #25685, GitHub Pull Request #25835, and GitHub Pull Request #25836. The tracking issue is Apache JIRA Issue CAMEL-24428.
Workarounds
- Add an onException handler to each Knative route that explicitly sets the response body, ensuring the framework never writes the raw exception back to the caller.
- Deploy a reverse proxy or API gateway in front of the Camel service that strips response bodies on 5xx status codes.
- Restrict network reachability to Knative consumer endpoints to known internal callers until the upgrade is applied.
# Configuration example: pin to the fixed version in Maven
# pom.xml dependency management
# <dependency>
# <groupId>org.apache.camel</groupId>
# <artifactId>camel-knative</artifactId>
# <version>4.23.0</version>
# </dependency>
# Route-level fallback for deployments awaiting upgrade (Camel DSL)
# onException(Exception.class)
# .handled(true)
# .setHeader("CamelHttpResponseCode", constant(500))
# .setBody(constant(""));
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

