CVE-2026-85251

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.

• CWE-200

• https://camel.apache.org/security/CVE-2026-85251.htmlMitigation, Patch, Vendor Advisory
• https://github.com/apache/camel/pull/25830Issue Tracking, Patch
• https://github.com/apache/camel/pull/25937Issue Tracking, Patch
• https://github.com/apache/camel/pull/25938Issue Tracking, Patch
• https://issues.apache.org/jira/browse/CAMEL-24452Issue Tracking, Vendor Advisory

Published

Oct 19, 2026

Last Modified

Nov 3, 2026

Status

Analyzed

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-85246Generation of Error Message Containing Sensitive Information…5.3
• CVE-2026-85247Improper Certificate Validation vulnerability in Apache Came…5.9
• CVE-2026-85248Concurrent Execution using Shared Resource with Improper Syn…5.9
• CVE-2026-85249Improper Input Validation vulnerability in Apache Camel Tika…6.5
• CVE-2026-8525Heap buffer overflow in ANGLE in Google Chrome on Mac prior …8.3
• CVE-2026-85250Improper Restriction of XML External Entity Reference vulner…7.5
• CVE-2026-85254Improper Handling of Case Sensitivity vulnerability in Apach…6.5
• CVE-2026-85257Generation of Error Message Containing Sensitive Information…5.3
• CVE-2026-8526Out of bounds write in WebRTC in Google Chrome prior to 148.…8.8
• CVE-2026-85260Insertion of Sensitive Information into Log File vulnerabili…5.5
• CVE-2026-85267A Cross-Site WebSocket Hijacking vulnerability in Cloud Shel…8.7
• CVE-2026-85268A Cross-Site Scripting (XSS) (CWE-79) vulnerability in the a…8.7