Live › vulnerability › CVE-2026-85251
Go to dashboardWhen followRedirects is enabled, the Apache Camel HTTP component re-attaches OAuth2 bearer tokens and basic or digest credentials to whatever host a redirect Location header names. A remote server or anyone who controls its responses can collect those credentials by answering with a redirect to a host it controls.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Applications that use the Apache Camel HTTP component with followRedirects=true on endpoints that send OAuth2 bearer tokens or basic or digest credentials. The exposure depends on the remote server being able to return redirects, so calls to third-party or untrusted endpoints carry the most risk. Routes with followRedirects off, or with no credentials on the endpoint, are not exposed to this leak.
No product ranges from the sources yet.
mvn dependency:tree | grep camel-http or the Camel version in your build file; affected releases are 4.0.0 to before 4.18.5 and 4.19.0 to before 4.22.1followRedirects=true on HTTP or HTTP4 endpoints that carry OAuth2 or basic credentials4.23.04.18.54.22.1followRedirects=false on endpoints that carry credentials and handle redirects explicitly in the routeEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Apache Camel HTTP component.
This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.
Two paths handed credentials to a redirect target, which is a host chosen by the remote server rather than by the route, once followRedirects=true. OAuth2ClientConfigurer registers its interceptor with addRequestInterceptorFirst, and HttpClient runs protocol-level request interceptors inside ProtocolExec, which sits below RedirectExec in the exec chain; the interceptor therefore ran again for every redirect hop and re-attached Authorization: Bearer to whatever host the Location header named. Separately, credentials were registered against an AuthScope matching any host, so basic and digest credentials were presented to a redirect target as well. A remote endpoint - or anyone who can influence its responses - could therefore collect the bearer token or the configured credentials simply by answering with a redirect to a host it controls.
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. Credentials are now sent only to the authority the endpoint was configured with, and are not re-attached when a redirect crosses to another host. For deployments that cannot upgrade immediately, set followRedirects=false on endpoints that carry credentials, and handle any redirect explicitly in the route so that the destination is chosen by the route rather than by the remote server.
This page as .md · .json · in your agent: get_signal("CVE-2026-85251")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.