Skip to main content

CVE-2026-85251: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor in Apache Software Foundation Apache Camel

0
High
VulnerabilityCVE-2026-85251cvecve-2026-85251cwe-200
Published: 10/19/2026 (10/19/2026, 10:36:09 UTC)
Source: CVE Database V5
Vendor/Project: Apache Software Foundation
Product: Apache Camel

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.

CVSS v3.1

Score 7.5high

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected software

Apache Software Foundation

Apache Camel

Affected versions
>=4.0.0 <4.18.5>=4.19.0 <4.22.1
Apache Software Foundation/org.apache.camel:camel-http
pkg:maven/Apache Software Foundation/org.apache.camel:camel-http
Affected versions
>=4.0.0 <4.18.5>=4.19.0 <4.22.1

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/19/2026, 11:03:47 UTC

Technical Analysis

The vulnerability in Apache Camel HTTP component involves exposure of sensitive information (bearer tokens and credentials) to unauthorized actors due to improper handling of HTTP redirects when followRedirects=true. Specifically, OAuth2ClientConfigurer's interceptor re-attaches Authorization: Bearer headers on every redirect hop, including to hosts chosen by the remote server, not the route. Similarly, basic and digest credentials registered with a broad AuthScope are sent to redirect targets. This allows a remote endpoint or an attacker controlling redirect responses to capture sensitive credentials. The issue affects Apache Camel versions >=4.0.0 <4.18.5 and >=4.19.0 <4.22.1. The fix, available in 4.18.5, 4.22.1, and 4.23.0, restricts credentials to be sent only to the originally configured authority and prevents re-attachment on cross-host redirects. Temporary mitigation involves setting followRedirects=false and handling redirects explicitly in routes.

Potential Impact

An attacker controlling a redirect response can obtain sensitive credentials such as OAuth2 bearer tokens or basic/digest authentication credentials by causing the client to follow redirects to attacker-controlled hosts. This leads to unauthorized disclosure of sensitive information, potentially compromising authentication and access controls. The CVSS 3.1 score is 7.5 (High), reflecting network attack vector, low complexity, no privileges required, no user interaction, and high confidentiality impact without integrity or availability impact.

Mitigation Recommendations

A fix is available in Apache Camel versions 4.18.5, 4.22.1, and 4.23.0. Users should upgrade to one of these versions to resolve the vulnerability. For users unable to upgrade immediately, it is recommended to set followRedirects=false on endpoints that carry credentials and to handle redirects explicitly within the route, ensuring that redirect destinations are controlled by the route rather than the remote server.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
apache
Date Reserved
2026-09-03T16:31:52.210Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6ad5f59d2cdf04f656435535

Added to database: 10/19/2026, 10:49:01 UTC

Last enriched: 10/19/2026, 11:03:47 UTC

Last updated: 10/19/2026, 19:06:46 UTC

Views: 10

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses