Apache Camel: Camel-Platform-HTTP Unintended Proxy Mode via Prefix Path Matching
CVSS score
4.8
EPSS probability
—
Risk score
0.5
Published
6 h ago
Etkilenen ürün ve sürüm için yayımlanan güvenlik güncellemesini uygulayın.
Impact on My Inventory
Only the personal products you have added to your account are assessed; an organisation's inventory does not appear here.
Checking session…
Vulnerability description
CVE AI research
DayBreach AI Explanation
Verified against sourcesSources read
1
Source agreement
Tam uyum
Evidence confidence
%55
Short explanation
CVE-2026-85316 involves an insufficient granularity of access control vulnerability in the Apache Camel Platform HTTP component. The component determines whether an endpoint runs in proxy mode by testing if its configured path starts with the proxy string rather than matching the path exactly, leading to request forgery and unintended traffic relaying.
This vulnerability causes endpoints to act as proxies and relay traffic without the route author's intent, creating a request forgery primitive and exposing whatever resources the forwarding path can reach.
What should be done?
- Upgrade to Apache Camel 4.23.0 or the corresponding LTS streams 4.18.5 and 4.22.1
- Rename any endpoint path that begins with proxy but is not intended to be a proxy for deployments unable to upgrade immediately
Chain of evidence and sources
CVE-2026-85316, Apache Camel Platform HTTP bileşenindeki yetersiz erişim denetimi granülaritesinden kaynaklanmaktadır.
Etkilenen sürümler arasında 4.0.0 ile 4.18.5 öncesi ve 4.19.0 ile 4.22.1 öncesi sürümler bulunmaktadır.
Sorun, proxy modunun tam eşleşme yerine önek testi ile seçilmesinden kaynaklanmaktadır.
Show the technical text from the sources
Insufficient Granularity of Access Control vulnerability in Apache Camel Platform HTTP component. This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. The component decided whether an endpoint ran in proxy mode by testing whether its configured path started with the string proxy, rather than by matching the path exactly. Any endpoint whose path merely begins with those characters - proxyStatus, proxy-config, proxying and so on - therefore became a proxy endpoint without the route author asking for it. A proxy endpoint forwards requests onward, so an endpoint that was intended to serve its own content instead relays traffic on behalf of whoever calls it, which is both a request forgery primitive and an exposure of whatever the forwarding path can reach. 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. Proxy mode is now selected by an exact path match rather than by prefix. For deployments that cannot upgrade immediately, rename any endpoint path that begins with proxy but is not intended to be a proxy.
CVSS vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
CWE: CWE-1220
Explanation produced with the local gemini-flash-lite-latest model. Numerical metrics and the KEV, patch and exploit statuses are not determined by AI.
IMPACT: Affected Products and Software
Affected Products
The following products are affected by CVE-2026-85316 vulnerability. Where our threat engine knows the exact affected versions, they are listed below.
| ID | VENDOR | PRODUCT | ACTION |
|---|---|---|---|
| 1 | Apache Software Foundation | Apache Camel | View |
RED HAT CSAF/VEX: Product Impact Check
SCORING: CVSS from Multiple Sources
CVSS Scores
The Common Vulnerability Scoring System is a standardised framework for assessing the severity of vulnerabilities in software and systems. We collect and display CVSS scores from several sources for each CVE.
| SCORE | VERSION | SEVERITY | VECTOR | SOURCE |
|---|---|---|---|---|
| 4.8 | CVSS V31 | MEDIUM | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N | NVD |
| 4.8 | CVSS V3_1 | MEDIUM | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N | CVE CNA |
Patch and Remediation Guide
Solution & Remediation Advisory
6 doğrulanmış yama veya düzeltilmiş sürüm kanıtı bulundu.
Backport to camel-4.22.x, released in 4.22.1 (commit 260989268cbc6d258b1fcba63770be8ebbec40cb)
Open sourceBackport to camel-4.18.x, released in 4.18.5 (commit af1efbcccf5882b1ef0094db718972da3190e7e9)
Open sourceFix on main, released in 4.23.0 (commit 7abf13b2b314f40b8e76af3ba655266b57ff5e20)
Open sourceBackport to camel-4.22.x, released in 4.22.1 (commit 260989268cbc6d258b1fcba63770be8ebbec40cb)
Open sourceBackport to camel-4.18.x, released in 4.18.5 (commit af1efbcccf5882b1ef0094db718972da3190e7e9)
Open sourcePublic exploit and active exploitation status
Verified exploit intelligence
No verified public PoC, exploit repository or Metasploit module has been found for this CVE yet.
Weakness Classification and Attack Patterns (CWE & CAPEC)
CWE - Common Weakness Enumeration
While CVE identifies specific instances of vulnerabilities, CWE categorises the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-85316 is associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-85316 weaknesses.
Attack Vector and Accessibility
Official Sources and Advisories
CVSS Vector Radar Chart
4.8 / 10Vulnerability Scoring Details
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:NYama doğrulandı
Weakness Type (CWE & CAPEC)
Similar Vulnerabilities
Get this vulnerability through the API
Affected products, version ranges, exploitation status and patch information in a single request, with a free key.
curl -H "x-api-key: $DAYBREACH_API_KEY" \ "https://api.daybreach.dev/api/v1/intel/cves/CVE-2026-85316"