CVE-2026-78164
Description
A flaw was found in Apache Camel HTTP producer components. When processing messages that override destination addresses, the service improperly evaluates user-controlled header values through its internal configuration resolver. A remote attacker can exploit this vulnerability by submitting requests containing crafted property placeholders. This flaw primarily leads to information disclosure, allowing the attacker to retrieve sensitive system properties, environment variables, and cloud secrets, or trigger unintended application actions.
Mitigation
--- 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)
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 8.2 | N/A | 8.2 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | High |
| Integrity Impact | Low | N/A | Low |
| Availability Impact | None | N/A | None |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
