Severity:
CVSS 3.1: 7.5 (high) CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Affected versions:
- Apache Camel (org.apache.camel:camel-http) 4.0.0 before 4.18.5
- Apache Camel (org.apache.camel:camel-http) 4.19.0 before 4.22.1
- Apache Camel (org.apache.camel:camel-http) 4.18.5 unaffected
- Apache Camel (org.apache.camel:camel-http) 4.22.1 unaffected
- Apache Camel (org.apache.camel:camel-http) 4.23.0 unaffected
Description:
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.
Solution:
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.
Work Arounds:
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.
Credit:
Claude Security (finder)
Andrea Cosentino (remediation developer)
References:
https://camel.apache.org/security/CVE-2026-85251.html
https://issues.apache.org/jira/browse/CAMEL-24452
https://github.com/apache/camel/pull/25830
https://github.com/apache/camel/pull/25937
https://github.com/apache/camel/pull/25938
https://camel.apache.org/
https://www.cve.org/CVERecord?id=CVE-2026-85251
