cve.bz

CVE-2026-85251 apache camel

7.5 highEPSS 0.7%Fix available

High (7.5) in apache camel. EPSS 0.7% estimated probability of exploitation activity in the next 30 days.

On this page
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.

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
EPSS
0.7% (unchanged from 0.7% a week ago) estimated probability of exploitation activity in the next 30 days; 52nd percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-10-19. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-85251 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-85251?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-85251?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-85251 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-85251

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-85251](https://cve.bz/cve/badge/CVE-2026-85251.svg)](https://cve.bz/cve/CVE-2026-85251)

HTML:

<a href="https://cve.bz/cve/CVE-2026-85251"><img src="https://cve.bz/cve/badge/CVE-2026-85251.svg" alt="CVE-2026-85251"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Camelfrom 4.0.0 before 4.18.5
Apache Software Foundation Apache Camelfrom 4.19.0 before 4.22.1

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as Important severity because unauthenticated remote services can capture sensitive credentials without interaction whenever HTTP redirect following is enabled on authenticated Camel routes. In Red Hat integration environments such as Red Hat build of Apache Camel, the risk is elevated if routes interact with external or partially trusted endpoints while transmitting OAuth bearer tokens or basic authentication data. However, routes that connect solely to trusted internal services or do not automatically follow redirects are not exposed to cross-host credential leakage.

Red Hat's mitigation

--- CME Mitigation Guidance (2026-10-20) ---

Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.

The highest-value action is to prevent camel-http from re-attaching authentication credentials across differing authorities during redirect hops: upgrade to Apache Camel 4.18.5, 4.22.1, or 4.23.0 (or the fixed Camel Http builds), which restrict OAuth2 token attachment and basic authentication AuthScope credentials strictly to the endpoint's configured scheme, host, and effective port, closing all 2 injection vectors (HTTP redirect re-attaching OAuth2 bearer token to third-party host, HTTP redirect sending basic or digest credentials to wildcard AuthScope host). Until patched, this is a concern on Camel HTTP endpoints configured with followRedirects=true using OAuth2 bearer tokens or basic/digest authentication, so 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. As a compensating measure, restricts outbound network egress so that HTTP redirect requests to unauthorized external destinations are blocked, preventing transmission of credentials to attacker-controlled hosts. These controls limit blast radius and contain exploitation, but they do not fix the underlying credential-forwarding defect — apply the upstream patch to fully remediate.

Highest-impact CME: CME-208 Outbound Network Egress Restriction (SSRF Blast Radius Containment) (medium)

ProductPackageStateAdvisory
Red Hat build of Apache Camel 4 for Quarkus 3camel-httpAffected
Red Hat build of Apache Camel for Spring Boot 4camel-httpAffected
Red Hat Fuse 7camel-httpOut of support scope

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-85251.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

  • oscerd/CVE-2026-85251 Harbor Check: matches CVE 0 stars, Java, created
    Reproducer for CVE-2026-85251 — Apache Camel camel-http credential disclosure on redirect (CWE-200); Spring Boot, affected vs fixed

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-200 (59).

References

Check your stackJSON