{"id":"CVE-2026-85316","title":"Apache Camel: Camel-Platform-HTTP Unintended Proxy Mode via Prefix Path Matching","summary":"Insufficient Granularity of Access Control vulnerability in Apache Camel Platform HTTP component.\n\nThis issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.\n\nThe component decided whether an endpoint ran in pr…","severity":"medium","cvss":4.8,"cvssVector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N","cvssSource":"cna","cwe":["CWE-1220"],"vendor":"Apache Software Foundation","product":"org.apache.camel:camel-platform-http","affected":["org.apache.camel:camel-platform-http >= 4.0.0 < 4.18.5","org.apache.camel:camel-platform-http >= 4.19.0 < 4.22.1"],"published":"2026-10-19","updated":"2026-10-19","sourceUpdated":"2026-10-19T10:43:00.504Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-85316","references":[{"url":"https://camel.apache.org/security/CVE-2026-85316.html","label":"Apache Camel Security Advisory - CVE-2026-85316"},{"url":"https://issues.apache.org/jira/browse/CAMEL-24455","label":"CAMEL-24455"},{"url":"https://github.com/apache/camel/pull/25833","label":"Fix on main, released in 4.23.0 (commit 7abf13b2b314f40b8e76af3ba655266b57ff5e20)"},{"url":"https://github.com/apache/camel/pull/25940","label":"Backport to camel-4.22.x, released in 4.22.1 (commit 260989268cbc6d258b1fcba63770be8ebbec40cb)"},{"url":"https://github.com/apache/camel/pull/25942","label":"Backport to camel-4.18.x, released in 4.18.5 (commit af1efbcccf5882b1ef0094db718972da3190e7e9)"}],"tags":["cve.org"],"ingestedAt":"2026-10-19T12:27:23.807Z","slug":"CVE-2026-85316","body":"## Overview\n\nInsufficient Granularity of Access Control vulnerability in Apache Camel Platform HTTP component.\n\nThis issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.\n\nThe 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.\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. 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.\n\n## Affected\n\n- `org.apache.camel:camel-platform-http >= 4.0.0 < 4.18.5`\n- `org.apache.camel:camel-platform-http >= 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. Proxy mode is now selected by an exact path match rather than by prefix.\n\n### Workarounds\n\nFor deployments that cannot upgrade immediately, rename any endpoint path that begins with proxy but is not intended to be a proxy.","depth":"sunlit","depthScore":26,"depthScoreParts":{"impact":26.4,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}