CVE-2026-84180
Generation of Error Message Containing Sensitive Information vulnerability in Apache Camel Knative…
- Risk score
- 42/100
- CVSS
- 5.3 v3.1
- Exploit chance (30 days)
- 0.6%
- Published
- 19 Oct 2026
Open in the live forecast Today's forecast
What to know
- What it is
- Generation of Error Message Containing Sensitive Information vulnerability in Apache Camel Knative component. This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. When processing of an exchange failed on the consumer side, the Knative HTTP consumer wrote the resulting exception back to…
- Affected
- Apache Camel before 4.18.5, 4.22.1
- Fix
- Upgrade Apache Camel to 4.18.5 or 4.22.1 (whichever matches your release line), or later.
- Exploitation
- No known exploitation
Story map
At a glance
Apache Camel: Red, act today. Apache Camel has a 'Path Traversal' vulnerability in its Azure Files component, allowing an attacker to access files outside the intended directory. An attacker could read, write, or delete files on the remote server.
The flaws
- CVE-2026-84180: Generation of Error Message Containing Sensitive Information vulnerability in Apache Camel Knative… (CVSS 5.3 · EPSS 1%)
- CVE-2026-79986: Path traversal (CVSS 9.1 · EPSS 1%)
- CVE-2026-78162: Unsafe deserialisation can lead to remote code execution (CVSS 9.8 · EPSS 1%)
- CVE-2026-79983: Path traversal (CVSS 9.1 · EPSS 1%)
The fix
Upgrade Apache Camel: 4.18.5 · 4.22.1 · 4.23.0 or later on your release line
Who is exposed: {'products': ['Apache Camel'], 'packages': [], 'versions': ['4.0.0 before 4.18.5', '4.19.0 before 4.22.1']}
Where it stands
- No known exploitation
Connects to
- Same weakness: CWE-209 (CWE-209). 23 other warnings in 30 days
- Same product: Earlier Apache Camel warnings. 23 in the last 90 days
Why it is Yellow
- CVSS 5.3 medium
References
Original description
Generation of Error Message Containing Sensitive Information vulnerability in Apache Camel Knative component. This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. When processing of an exchange failed on the consumer side, the Knative HTTP consumer wrote the resulting exception back to the remote caller as the response body, including its class name, message and stack trace. An external sender could therefore provoke a failure and read internal detail about the deployment: class and package names, file system or host names carried in exception messages, and the shape of the route. That detail is useful for building a more targeted attack, and where an exception message embeds configuration or connection strings it is disclosure in its own right. camel-knative was the remaining HTTP-family consumer that had not been aligned with the muteException behaviour established for the other HTTP consumers by CAMEL-23651. Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. 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. Set muteException=false to restore the previous output. For deployments that cannot upgrade immediately, add an onException handler that sets the response body explicitly, so that the framework never writes the exception back to the caller.
Last activity 19 Oct 2026. Patch Forecast updates every hour.