---
id: "CVE-2026-85316"
kind: "vulnerability"
aliases: ["CVE-2026-85316"]
title: "Apache Camel: path prefix match turns ordinary HTTP endpoints into proxies"
severity: "medium"
cvss: 4.8
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["apache-camel", "java", "package", "platform-http", "self-hosted"]
not_affected_if: ["fixed-version", "no-proxy-prefixed-paths"]
published_at: "2026-10-19T11:17:24+00:00"
first_seen_at: "2026-10-23T21:57:18+00:00"
updated_at: "2026-10-25T04:33:29+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-85316", "first_seen_at": "2026-10-23T21:57:18+00:00"}]
---

# Apache Camel: path prefix match turns ordinary HTTP endpoints into proxies

Apache Camel's Platform HTTP component treated any endpoint path beginning with 'proxy' as a proxy endpoint, such as proxyStatus or proxy-config. Those endpoints then forward requests onward, letting callers make the server relay traffic and reach whatever the forwarding path can access.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Search Camel route definitions for platform-http endpoint paths that start with `proxy` but are not meant to be proxies, such as `proxyStatus` or `proxy-config`
- Check the Camel version in the build file, for example `mvn dependency:tree | grep camel-platform-http` and confirm it is below `4.18.5` on the 4.18 line or below `4.22.1` on the 4.22 line

## Fix

- Upgrade Apache Camel to `4.23.0`
- On the 4.18.x LTS stream, upgrade to `4.18.5`
- On the 4.22.x LTS stream, upgrade to `4.22.1`
- If an upgrade is not possible now, rename any endpoint path starting with `proxy` that is not intended as a proxy

## Timeline

- 2026-10-23T21:57:18+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-85316

## 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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_