Apache Camel is a widely used enterprise integration framework; this flaw allows remote placeholder resolution that can leak secrets or invoke bean methods leading to RCE, risking broad service compromise.
CVE-2026-78164
Header-supplied URI placeholders enable RCE and secret disclosure in Apache Camel HTTP components
Is CVE-2026-78164 being exploited?
Not confirmed. CVE-2026-78164 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.
How severe is CVE-2026-78164?
CVE-2026-78164 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-78164?
Yes. A fix has been recorded for CVE-2026-78164. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-78164 affect?
CVE-2026-78164 affects Apache Camel 4.0.0 - 4.18.4, Apache Camel 4.19.0 - 4.22.0, Components: camel-http, camel-http-common, camel-vertx-http, camel-undertow, camel-netty-http, 4.14.x and earlier: no fix (EOL). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-78164?
Upgrade to 4.23.0 / 4.22.1 / 4.18.5; or strip CamelHttpUri/CamelRestHttpUri at trust boundary / set skipControlHeaders on camel-http
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers can supply CamelHttpUri/CamelRestHttpUri headers to trigger property-placeholder resolution, exposing secrets, invoking bean methods or achieving remote code execution.
Immediate action required
- affected>= 4.0.0 and < 4.18.5
- affected>= 4.19.0 and < 4.22.1
- affected>= 4.15.0 and < 4.18.5
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.