Credential leak to redirect targets in Apache Camel HTTP component
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- Partial Red Hat: 3 without a fix
Attack profile from CVSS 3.1 · CNA. Fix status from CNA and Red Hat. Impact type from CWE-200.
Summary
Apache Camel from 4.0.0 before 4.18.5 and from 4.19.0 before 4.22.1 sends credentials to redirect targets when followRedirects=true (CWE-200). The OAuth2 bearer token is re-attached on each redirect hop, and basic and digest credentials are matched to any host. A remote endpoint, or anyone who can influence its responses, can collect them by redirecting to a host it controls.
Written with Claude Haiku 5.5 from the sources below · 2026-10-28
Description from the CNA
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
Upgrade Apache Camel to 4.23.0, or to 4.18.5 on the 4.18.x LTS stream or 4.22.1 on the 4.22.x LTS stream. Red Hat Fuse 7 has no fix planned, and Red Hat build of Apache Camel 4 for Quarkus 3 and Red Hat build of Apache Camel for Spring Boot 4 have no fix available. Until upgrading, set followRedirects=false on endpoints that carry credentials and handle redirects explicitly in the route.
Written with Claude Haiku 5.5 from the sources below · 2026-10-28
- Fix · CNA Apache Camel (Apache Software Foundation) Fixed in 4.18.5, 4.22.1, 4.23.0
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
Apache Camel 4.18.5, 4.22.1
39 records Highest priority Priority HIGH 6 HIGH, 9 MEDIUM, 24 LOW
Other records, highest priority first
- TI-2026-76322 Unsafe deserialization in Apache Camel camel-hazelcastPriority HIGH 82
- TI-2026-76339 Path traversal in Apache Camel azure-files componentPriority HIGH 74
- TI-2026-76330 Path traversal in Apache Camel FTP consumer escapes polled directoryPriority HIGH 74
Vendor assessments
Red Hat
Red Hat rating: Important. Red Hat's page for this CVE →
| Product | Status | Plan or fix |
|---|---|---|
| Red Hat Fuse 7 | Affected | No fix planned: Out of support scope |
| Red Hat build of Apache Camel 4 for Quarkus 3 | Affected | No fix yet |
| Red Hat build of Apache Camel for Spring Boot 4 | Affected | No fix yet |
Timeline
- 2026-10-19 Threatist record created from CVE-2026-85251
- 2026-10-19 Alias added: GHSA-2j38-4xg3-6926
- 2026-10-19 CISA SSVC decision points changed
- 2026-10-19 Priority changed: MEDIUM → LOW
- 2026-10-20 Affected versions changed · Red Hat
- 2026-10-20 CVSS score added · Red Hat
- 2026-11-04 EPSS moved to the 50th–90th percentile
- 2026-11-05 Priority changed: LOW → MEDIUM
References
Patch 4
- Apache Camel Security Advisory - CVE-2026-85251
- Fix on main, released in 4.23.0 (commit 3a6c27bfae04e528f5a76494db6d6d97b9234551)
- Backport to camel-4.22.x, released in 4.22.1 (commit b0399b181d26cd8b136fa98b54ec8e5c283338da)
- Backport to camel-4.18.x, released in 4.18.5 (commit e23332aec12f7ec3a841e52d1821e2a580c2fbc7)
Advisory 1
More Apache Camel vulnerabilities
- TI-2026-76322 Unsafe deserialization in Apache Camel camel-hazelcast CVSS 4.0CRITICAL 10.0
- TI-2026-18973 Apache Camel: Camel-Keycloak: Cross-Realm Token Acceptance Bypass in KeycloakSecurityPolicy CVSS 3.1CRITICAL 9.1
- TI-2026-76339 Path traversal in Apache Camel azure-files component CVSS 3.1CRITICAL 9.1
- TI-2026-76330 Path traversal in Apache Camel FTP consumer escapes polled directory CVSS 3.1CRITICAL 9.1
- TI-2025-20435 Apache Camel: Camel Message Header Injection via Improper Filtering CVSS 3.1MEDIUM 5.6
- TI-2026-34899 Apache Camel: Camel-CXF Message Header Injection via Missing Inbound Filtering CVSS 3.1CRITICAL 9.8
Sources
- CVE-2026-85251 · CVE Program
- CVE-2026-85251 · NVD
- FIRST EPSS
- GHSA-2j38-4xg3-6926 · GitHub Advisory Database · CC BY 4.0
- CVE-2026-85251 · Red Hat security data · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences