# CVE-2026-85251: Apache Camel: Camel-HTTP Credential Disclosure to Cross-Host Redirect Targets

> Attackers can steal OAuth2 or basic credentials by triggering redirects to malicious hosts when followRedirects is enabled in Apache Camel HTTP components.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-2j38-4xg3-6926

## What is CVE-2026-85251?

CVE-2026-85251 is a high-severity vulnerability in Apache Camel, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-85251?


## How do I fix CVE-2026-85251?

No fix has been published for CVE-2026-85251 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-85251 being exploited?

There is no known exploitation of CVE-2026-85251 in the wild and no public exploit code.

Public exploit code:

- Reproducer for CVE-2026-85251 — Apache Camel camel-http credential disclosure on redirect (CWE-200); Spring Boot, affected vs fixed (github_poc): https://github.com/oscerd/CVE-2026-85251

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-85251 and fix it if it is affected.

What it is: CVE-2026-85251 is a high-severity vulnerability in Apache Camel, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-85251 in the wild and no public exploit code.

Affected product: Apache Camel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-85251/ (Markdown: https://insights.sbomify.com/CVE-2026-85251/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-85251
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-85251
- OSV: https://osv.dev/vulnerability/CVE-2026-85251

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-85251/
Summaries are generated and may contain mistakes; the official description above is the record.