CVE-2026-85251: Apache Camel HTTP component credential leakage on redirect

CVE-2026-85251 · Severity: high · CVSS 7.5 · Published 2026-10-19

Apache Camel is an integration framework that processes data flows between systems, including HTTP-based API calls. When followRedirects is enabled, the HTTP component incorrectly sends authentication credentials (bearer tokens and basic/digest credentials) to servers designated by redirect responses, rather than only to the originally configured endpoint. An attacker controlling a remote server or intercepting redirects could capture these credentials to compromise API authentication.

Technologies: Apache Camel. Vendors: Apache.

Quick answers

Is CVE-2026-85251 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-85251 being exploited in the wild.
How severe is CVE-2026-85251?
High severity, with a CVSS score of 7.5, 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-85251?
Yes: fixed in Apache Camel 4.23.0, 4.18.5, 4.22.1. Until then: Set followRedirects=false on HTTP endpoints that carry credentials and handle redirects explicitly in the route so the destination is chosen by the integration logic rather than by the remote server. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-85251 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-85251?
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: Apache Camel 4.23.0, 4.18.5, 4.22.1

Set followRedirects=false on HTTP endpoints that carry credentials and handle redirects explicitly in the route so the destination is chosen by the integration logic rather than by the remote server.

Technical details

OAuth2 bearer tokens and basic/digest credentials are re-attached by request interceptors during HTTP redirects across hosts due to interceptor execution order in the underlying HttpClient library and overly broad AuthScope matching. The vulnerability requires followRedirects=true and credentials to be configured on the endpoint; an attacker must be able to influence the redirect target via the Location header (either by operating the remote endpoint or via MITM). Credentials are leaked to the attacker-controlled redirect destination.

Affected products

  • Apache Camel 4.0.0 before 4.18.5, 4.19.0 before 4.22.1

Timeline

  • 2026-10-19: disclosed

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