# CVE-2026-85316: Apache Camel: Camel-Platform-HTTP Unintended Proxy Mode via Prefix Path Matching

> Attackers can force unintended proxy mode in Apache Camel HTTP endpoints via prefix path matching, enabling Server-Side Request Forgery and unauthorized traffic forwarding.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-7rmf-gx38-35x6

## What is CVE-2026-85316?

CVE-2026-85316 is a medium-severity server-side request forgery vulnerability in Apache Camel, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

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

Weakness: CWE-1220 (Insufficient Granularity of Access Control)

## Which versions are affected by CVE-2026-85316?


## How do I fix CVE-2026-85316?

No fix has been published for CVE-2026-85316 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-85316 being exploited?

There is no known exploitation of CVE-2026-85316 in the wild and no public exploit code.

Public exploit code:

- Reproducer for CVE-2026-85316 — Apache Camel camel-platform-http unintended proxy mode from a path prefix (CWE-1220). Camel Spring Boot + Camel Quarkus. (github_poc): https://github.com/oscerd/CVE-2026-85316

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-85316 and fix it if it is affected.

What it is: CVE-2026-85316 is a medium-severity server-side request forgery vulnerability in Apache Camel, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-85316 in the wild and no public exploit code.

Affected product: Apache Camel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-85316/ (Markdown: https://insights.sbomify.com/CVE-2026-85316/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-85316
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-85316
- OSV: https://osv.dev/vulnerability/CVE-2026-85316

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-85316/
Summaries are generated and may contain mistakes; the official description above is the record.