Is CVE-2026-85316 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-85316 being exploited in the wild.

How severe is CVE-2026-85316?

Medium severity, with a CVSS score of 4.8, published 19 October 2026.

Which products and versions are affected?

Apache Camel 4.0.0 before 4.18.5, 4.19.0 before 4.22.1.

Is there a fix for CVE-2026-85316?

Yes: fixed in 4.18.5, 4.22.1, 4.23.0. Until then: For deployments unable to upgrade immediately, rename any endpoint path that begins with "proxy" but is not intended to be a proxy endpoint. [{"kind":"disclosed","at":"2026-10-15"},{"kind":"advisory","at":"2026-10-19"}] Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-85316 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-85316?

Check whether you run Apache Camel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-85316: Apache Camel insufficient granularity of access control in HTTP component

CVE-2026-85316 · Severity: medium · CVSS 4.8 · Published 2026-10-19

Apache Camel's HTTP component incorrectly identifies proxy endpoints by checking if the path starts with "proxy" rather than matching it exactly. This causes unintended endpoints like "proxyStatus" or "proxy-config" to become proxies, allowing attackers to relay traffic through the application to internal or external systems, potentially exposing sensitive data or enabling server-side request forgery attacks.

Technologies: Apache Camel. Vendors: Apache.

Quick answers

Is CVE-2026-85316 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-85316 being exploited in the wild.
How severe is CVE-2026-85316?: Medium severity, with a CVSS score of 4.8, published 19 October 2026.
Which products and versions are affected?: Apache Camel 4.0.0 before 4.18.5, 4.19.0 before 4.22.1.
Is there a fix for CVE-2026-85316?: Yes: fixed in 4.18.5, 4.22.1, 4.23.0. Until then: For deployments unable to upgrade immediately, rename any endpoint path that begins with "proxy" but is not intended to be a proxy endpoint.</anigation> <parameter name="timeline">[{"kind":"disclosed","at":"2026-10-15"},{"kind":"advisory","at":"2026-10-19"}] Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-85316 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-85316?: Check whether you run Apache Camel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 4.18.5, 4.22.1, 4.23.0

For deployments unable to upgrade immediately, rename any endpoint path that begins with "proxy" but is not intended to be a proxy endpoint.</anigation> <parameter name="timeline">[{"kind":"disclosed","at":"2026-10-15"},{"kind":"advisory","at":"2026-10-19"}]

Technical details

The vulnerability is a prefix-matching logic error in the HTTP component's proxy mode detection. Instead of comparing the configured path exactly against "proxy", the code checks whether the path merely begins with that string. An attacker can exploit this by requesting endpoints whose paths start with "proxy" to unwittingly trigger proxy behavior and forward requests to arbitrary destinations the application can reach.

Affected products

Apache Camel 4.0.0 before 4.18.5, 4.19.0 before 4.22.1

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.