{"id":"CVE-2026-84180","title":"Apache Camel: Camel-Knative Information Disclosure via Unmuted Consumer Exceptions","summary":"Generation of Error Message Containing Sensitive Information vulnerability in Apache Camel Knative component.\n\nThis issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.\n\nWhen processing of an exchange failed o…","severity":"medium","cvss":5.3,"cvssVector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","cvssSource":"cna","cwe":["CWE-209"],"vendor":"Apache Software Foundation","product":"org.apache.camel:camel-knative","affected":["org.apache.camel:camel-knative >= 4.0.0 < 4.18.5","org.apache.camel:camel-knative >= 4.19.0 < 4.22.1"],"published":"2026-10-19","updated":"2026-10-19","sourceUpdated":"2026-10-19T10:31:08.913Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-84180","references":[{"url":"https://camel.apache.org/security/CVE-2026-84180.html","label":"Apache Camel Security Advisory - CVE-2026-84180"},{"url":"https://issues.apache.org/jira/browse/CAMEL-24428","label":"CAMEL-24428"},{"url":"https://github.com/apache/camel/pull/25685","label":"Fix on main, released in 4.23.0 (commit 22cccdecdebd948bea1bcdd6a184345d013a3b1a)"},{"url":"https://github.com/apache/camel/pull/25835","label":"Backport to camel-4.22.x, released in 4.22.1 (commit ca9f326ada9703d32badabad2f32c66886ffa470)"},{"url":"https://github.com/apache/camel/pull/25836","label":"Backport to camel-4.18.x, released in 4.18.5 (commit 51e3f9047693120b4dd086dcceba16356f92e0aa)"}],"tags":["cve.org"],"ingestedAt":"2026-10-19T12:27:23.817Z","slug":"CVE-2026-84180","body":"## Overview\n\nGeneration of Error Message Containing Sensitive Information vulnerability in Apache Camel Knative component.\n\nThis issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.\n\nWhen 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.\n\nUpgrade 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.\n\n## Affected\n\n- `org.apache.camel:camel-knative >= 4.0.0 < 4.18.5`\n- `org.apache.camel:camel-knative >= 4.19.0 < 4.22.1`\n\n## Remediation\n\nUpgrade 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.\n\n### Workarounds\n\nFor 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.","depth":"sunlit","depthScore":29,"depthScoreParts":{"impact":29.2,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}