CVE-2026-85316: Insufficient Granularity of Access Control vulnerability in Apache Camel Platform HTTP component
CVE-2026-85316 key facts
- CISA KEV
- Not listed (catalogue checked )
- Highest advisory rating
- Medium
- CVSS base score
- 4.8 (Apache), 4.8 (Red Hat)
- Weakness
- CWE-918
- Fixed releases
- Apache: 4.18.5, 4.22.1
- Red Hat: 4.23.0, 4.18, 4.18.5, 4.22, 4.22.1
- Listed by VulniPulse
- Record changed
Ratings, versions and fixes are quoted from the vendor advisories that cover only CVE-2026-85316; each belongs to its advisory, not to every product listed. How records are collected and checked.
How do I fix CVE-2026-85316?
Upgrade to a fixed release named by the vendor:
- Apache: 4.18.5, 4.22.1
- Red Hat: 4.23.0, 4.18, 4.18.5, 4.22, 4.22.1
- Upgrade to Apache Camel 4.23.0, which fixes the issue. (Apache)
- Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. (Apache)
Vendor advisories for CVE-2026-85316
Apache
1 advisory- Advisory severityMedium4.8
Medium [CVE-2026-85316] Insufficient Granularity of Access Control vulnerability in Apache Camel Platform HTTP component
CVE-2026-85316Source published Source updated
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.…
- Affected products in this advisory
- Apache Camel Platform
- Source-reported affected versions
- 4.0.0 before 4.18.5
- 4.19.0 before 4.22.1
- Source-reported fixed versions
- 4.18.5
- 4.22.1
- Mitigation guidance
- 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.
- For deployments that cannot upgrade immediately, rename any endpoint path that begins with proxy but is not intended to be a proxy.
Red Hat
1 advisory- Advisory severityMedium4.8
Medium [CVE-2026-85316] Unauthorized request forwarding via improper path prefix matching
CVE-2026-85316Source published Source updated
Unauthorized request forwarding via improper path prefix matching. Red Hat rates this moderate (CVSS 4.8). Weakness: CWE-918. Affected products named by the advisory: OpenShift Serverless; Red Hat build of Apache Camel 4 for Quarkus 3; Red Hat build of Apache Camel for Spring Boot 4; Red Hat Fuse 7.
- Related products — impact not confirmed
- OpenShift Serverless
- Red Hat build of Apache Camel 4 for Quarkus 3
- Red Hat build of Apache Camel for Spring Boot 4
- Red Hat Fuse 7
- Source-reported affected versions
- < 4.0.0
- < 4.18.5
- < 4.19.0
- < 4.22.1
- Source-reported fixed versions
- 4.23.0
- 4.18
- 4.18.5
- 4.22
1 more entries in the full advisory.
- Mitigation guidance
- No mitigation guidance extracted; consult the source.
References
More Apache advisories
CVE-2026-85254Oct 19, 2026Improper Handling of Case Sensitivity vulnerability in Apache Camel Platform HTTPCVE-2026-84176Oct 19, 2026Permissive Cross-domain Policy with Untrusted Domains vulnerability in Apache CamelCVE-2026-66908Aug 24, 2026Apache Camel Platform authentication bypassCVE-2026-86336Nov 10, 2026Apache TomEE running on JDK 21 or later skips EJB method authorization checksCVE-2026-86531Nov 10, 2026The embedded OpenEJB HTTP server does not limit the size of incoming request bodiesCVE-2026-87758Nov 10, 2026The remote EJB client does not verify
Get an email when Apache publishes the next one.
See Apache's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).
iPhone and Android apps · New on the App Store
Get alerts for new CVEs on your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.