CVSS 3.1
8.2 highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:NHigh (8.2) in apache software foundation apache camel. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:NExplain CVE-2026-78164 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-78164?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-78164?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-78164 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Apache Software Foundation Apache Camel | from 4.0.0 before 4.18.5 |
| Apache Software Foundation Apache Camel | from 4.19.0 before 4.22.1 |
| Apache Software Foundation Apache Camel | from 4.15.0 before 4.18.5 |
Red Hat rates this Important.
This vulnerability is rated Important rather than Moderate because remote, unauthenticated attackers can exfiltrate sensitive credentials and application configuration without requiring prior access or administrative privileges. In Red Hat integration environments, Camel routes utilizing HTTP producer components propagate request metadata that may automatically resolve internal property placeholders. Consequently, external requests directed at standard reverse-proxy or bridging endpoints can expose backend secrets or invoke local bean operations across affected Apache Camel runtimes.
--- CME Mitigation Guidance (2026-10-20) ---
Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.
The highest-value action is to eliminate property placeholder resolution on message-supplied URI override headers in Apache Camel HTTP producer components: upgrade to Apache Camel 4.18.5, 4.22.1, or 4.23.0 (or the fixed Camel Http Common/Camel Http/Camel Vertx Http/Camel Undertow/Camel Netty Http builds), which remove property placeholder resolution on message-supplied URI override headers across HTTP producer helper methods, closing all 3 injection vectors (property placeholder injection via CamelHttpUri header, property placeholder injection via CamelRestHttpUri header, request-line placeholder injection via reverse-proxy consumers). Until patched, this is a concern on deployments using Apache Camel HTTP producer components handling untrusted message exchanges, so strip CamelHttpUri and CamelRestHttpUri headers at trust boundaries prior to routing to HTTP producers, or configure skipControlHeaders=true on camel-http endpoints. As a compensating measure, apply allowlist validation to inbound headers or strip unexpected control headers such as CamelHttpUri before message exchanges reach HTTP producers. These controls limit blast radius and contain exploitation, but they do not fix the underlying improper property placeholder evaluation defect — apply the upstream patch to fully remediate.
Highest-impact CME: CME-1309 Script Engine Restriction (Sandbox / Disable) (high)
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat build of Apache Camel 4 for Quarkus 3 | camel-http | Affected | |
| Red Hat build of Apache Camel 4 for Quarkus 3 | camel-http-common | Affected | |
| Red Hat build of Apache Camel 4 for Quarkus 3 | camel-netty-http | Affected | |
| Red Hat build of Apache Camel 4 for Quarkus 3 | camel-vertx-http | Affected | |
| Red Hat build of Apache Camel for Spring Boot 4 | camel-http | Affected | |
| Red Hat build of Apache Camel for Spring Boot 4 | camel-http-common | Affected | |
| Red Hat build of Apache Camel for Spring Boot 4 | camel-netty-http | Affected | |
| Red Hat build of Apache Camel for Spring Boot 4 | camel-undertow | Affected | |
| Red Hat build of Apache Camel for Spring Boot 4 | camel-vertx-http | Affected | |
| Red Hat Fuse 7 | camel-http | Affected | |
| Red Hat Fuse 7 | camel-http-common | Affected | |
| Red Hat Fuse 7 | camel-netty-http | Affected | |
| Red Hat Fuse 7 | camel-undertow | Affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-78164.
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-200 (59).