CVE-2026-85316
Received Received - Intake

Insufficient Access Control in Apache Camel Platform HTTP

Publication date: 2026-10-19

Last updated on: 2026-10-19

Assigner: Apache Software Foundation

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-19
Last Modified
2026-10-19
Generated
2026-10-19
AI Q&A
2026-10-19
EPSS Evaluated
N/A
NVD
CVE-2026-85316
EUVD
EUVD-2026-104204

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
Apache Software Foundation Apache Camel 4.0.0
Apache Software Foundation Apache Camel 4.19.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-1220 The product implements access controls via a policy or other feature with the intention to disable or restrict accesses (reads and/or writes) to assets in a system from untrusted agents. However, implemented access controls lack required granularity, which renders the control policy too broad because it allows accesses from unauthorized agents to the security-sensitive assets.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in Apache Camel Platform HTTP component allows unintended proxy mode activation. Endpoints with paths starting with 'proxy' (e.g., proxyStatus, proxy-config) incorrectly become proxy endpoints, forwarding traffic without explicit configuration. This enables request forgery and exposes internal paths.

Detection Guidance

Check Apache Camel Platform HTTP component versions. Run: mvn dependency:tree | grep camel-platform-http to identify affected versions (4.0.0 to 4.18.4, 4.19.0 to 4.22.0). Inspect endpoint paths for any starting with 'proxy' that are not intended as proxies.

Impact Analysis

An attacker could exploit this to turn your endpoint into a proxy, forwarding requests to unintended destinations. This may lead to data leaks, unauthorized access, or abuse of your infrastructure. Systems relying on path-based routing are particularly at risk.

Compliance Impact

This vulnerability could violate compliance by enabling unauthorized data exposure or access. GDPR may require breach notification if personal data is exposed. HIPAA could be compromised if protected health information is forwarded improperly. Organizations must patch to maintain compliance.

Mitigation Strategies
  • Upgrade Apache Camel to version 4.23.0 or apply the latest LTS patches (4.18.5 for 4.18.x, 4.22.1 for 4.22.x).
  • If immediate upgrade is not possible, rename any endpoint paths starting with 'proxy' that are not intended to be proxies.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-85316. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart