CVE-2026-85316
Last modified
CVE-2026-85316 is a medium-severity vulnerability rated 4.8/10 on the CVSS scale. 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.
Description
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Apache Software Foundation | Apache Camel | >= 4.0.0, < 4.18.5; >= 4.19.0, < 4.22.1 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-85316?
How severe is CVE-2026-85316?
How do I fix CVE-2026-85316?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-85310import_contacts Path Traversal in Groundhogg <= 4.7.1 versio…6.5
- CVE-2026-85311Missing Authorization vulnerability in Kings Plugins MarketK…5.3
- CVE-2026-85312Improper Input Validation vulnerability in Apache Camel Core…4.8
- CVE-2026-85313Permissive Cross-domain Policy with Untrusted Domains vulner…4.3
- CVE-2026-85314Improper Input Validation vulnerability in Apache Camel Mail…6.5
- CVE-2026-85315Generation of Error Message Containing Sensitive Information…5.3
- CVE-2026-85317Use of Cache Containing Sensitive Information vulnerability …4.8
- CVE-2026-85318Heap-based buffer overflow in Servicing Stack Updates allows…7.8
- CVE-2026-85319Allocation of resources without limits or throttling in Acti…7.5
- CVE-2026-8532Integer overflow in XML in Google Chrome prior to 148.0.7778…8.8
- CVE-2026-85320Use of uninitialized resource in Windows Print Spooler Compo…5.5
- CVE-2026-85321Allocation of resources without limits or throttling in Acti…7.5
Are you affected by CVE-2026-85316?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
