CVE-2025-14524: bearer token leak on cross-protocol redirect
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.68% (FIRST EPSS); higher than 52.4% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. Special conditions such as timing or configuration are required.
- Fixed version: curl curl 1a822275d333dc6da6043497160fd04c8fa48640, 8.14.2, 8.16.1; azl3 cmake 3.30.3-11 on Azure Linux 3.0 3.30.3-12; azl3 cmake 3.30.3-12 on Azure Linux 3.0 3.30.3-12.
Low priority for now. Upgrade to curl curl 1a822275d333dc6da6043497160fd04c8fa48640, 8.14.2, 8.16.1; azl3 cmake 3.30.3-11 on Azure Linux 3.0 3.30.3-12; azl3 cmake 3.30.3-12 on Azure Linux 3.0 3.30.3-12 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
When an OAuth2 bearer token is used for an HTTP(S) transfer, and that transfer performs a cross-protocol redirect to a second URL that uses an IMAP, LDAP, POP3 or SMTP scheme, curl might wrongly pass on the bearer token to the new target host.
- Published
- Jan 8, 2026
- Updated
- Sep 15, 2026
- EPSS
- 0.6% · 52th percentile
- CWE
- CWE-522
Report tools
Action score
21
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| haxx | curl | cpe:2.3:a:haxx:curl |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- haxx curl7.33.0 and later · before 8.18.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (curl). Independent of NVD's CPE analysis and usually ahead of it.
curl curl
- 8.17.0, 8.16.0, 8.15.0, 8.14.1, 8.14.0, 8.13.0, 8.12.1, 8.12.0, 8.11.1, 8.11.0, 8.10.1, 8.10.0 … (+24)affected
- 7.33.0 and later · before 8.14.2affected · semver
- 8.15.0 and later · before 8.16.1affected · semver
- 8.17.0 and later · before 8.18.0affected · semver
- 06c1bea72faabb6fad4b7ef818aafaa336c9a7aa and later · before 1a822275d333dc6da6043497160fd04c8fa48640affected · git
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.21 | curl | from 7.33.0 · before 8.14.1-r3 | 8.14.1-r3 |
| Alpine:v3.22 | curl | from 7.33.0 · before 8.14.1-r4 | 8.14.1-r4 |
| Alpine:v3.23 | curl | from 7.33.0 · before 8.18.0-r0 | 8.18.0-r0 |
| Debian:12 | curl | before 7.88.1-10+deb12u15 | 7.88.1-10+deb12u15 |
| Debian:13 | curl | before 8.14.1-2+deb13u4 | 8.14.1-2+deb13u4 |
| Debian:14 | curl | before 8.18.0~rc2-1 | 8.18.0~rc2-1 |
| openSUSE:Leap 15.6 | curl | before 8.14.1-150600.4.34.1 | 8.14.1-150600.4.34.1 |
| openSUSE:Leap 16.0 | curl | before 8.14.1-160000.4.1 | 8.14.1-160000.4.1 |
| openSUSE:Tumbleweed | curl | before 8.18.0-1.1 | 8.18.0-1.1 |
| Red Hat:hummingbird:1 | curl | before 0:8.19.0-3.hum1 | 0:8.19.0-3.hum1 |
| Red Hat:hummingbird:1 | libcurl | before 0:8.19.0-3.hum1 | 0:8.19.0-3.hum1 |
| Red Hat:hummingbird:1 | libcurl-devel | before 0:8.19.0-3.hum1 | 0:8.19.0-3.hum1 |
| Red Hat:hummingbird:1 | libcurl-minimal | before 0:8.19.0-3.hum1 | 0:8.19.0-3.hum1 |
| SUSE:Linux Enterprise Micro 5.2 | curl | before 8.14.1-150200.4.97.1 | 8.14.1-150200.4.97.1 |
| SUSE:Linux Enterprise Micro 5.3 | curl | before 8.14.1-150400.5.77.1 | 8.14.1-150400.5.77.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP7 | curl | before 8.14.1-150700.7.8.1 | 8.14.1-150700.7.8.1 |
| SUSE:Linux Enterprise Server 16.0 | curl | before 8.14.1-160000.4.1 | 8.14.1-160000.4.1 |
| SUSE:Linux Enterprise Server 16.0 | curl-mini | before 8.14.1-160000.4.1 | 8.14.1-160000.4.1 |
| SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | curl | before 8.0.1-11.111.1 | 8.0.1-11.111.1 |
| SUSE:Linux Micro 6.0 | curl | before 8.14.1-3.1 | 8.14.1-3.1 |
| SUSE:Linux Micro 6.1 | curl | before 8.14.1-slfo.1.1_4.1 | 8.14.1-slfo.1.1_4.1 |
Same product
haxx: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-22901curl 7.75.0 through 7.76.1 suffers from a use-after-free vulnerability resulting in already freed memory being used when a TLS 1.3 session t51Plan
- CVE-2023-38039When curl retrieves an HTTP response, it stores the incoming headers so that
they can be accessed later via the libcurl headers API.47Plan
- CVE-2024-2398HTTP/2 push headers memory-leak45Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-13034Jan 8, 2026 · No QUIC certificate pinning with GnuTLS23Monitor
- ← EarlierCVE-2025-14017Jan 8, 2026 · broken TLS options for threaded LDAPS25Monitor
- Later →CVE-2025-14819Jan 8, 2026 · OpenSSL partial chain store policy bypass21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| curl curl | 1a822275d333dc6da6043497160fd04c8fa48640 | Vendor (CNA) |
| curl curl | 8.14.2 | Vendor (CNA) |
| curl curl | 8.16.1 | Vendor (CNA) |
| curl curl | 8.18.0 | Vendor (CNA) |
| azl3 cmake 3.30.3-11 on Azure Linux 3.0 | 3.30.3-12 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 cmake 3.30.3-12 on Azure Linux 3.0 | 3.30.3-12 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 cmake 3.21.4-21 on CBL Mariner 2.0 | 3.21.4-22 · CBL-Mariner Releases | Microsoft (MSRC) |
| alpine:curl | 8.14.1-r3 · Alpine:v3.21 | Package registry (OSV) |
| alpine:curl | 8.18.0-r0 · Alpine:v3.23 | Package registry (OSV) |
| debian:curl | 7.88.1-10+deb12u15 · Debian:12 | Package registry (OSV) |
| opensuse:curl | 8.14.1-150600.4.34.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| red hat:curl | 0:8.19.0-3.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:libcurl | 0:8.19.0-3.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:libcurl-devel | 0:8.19.0-3.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:libcurl-minimal | 0:8.19.0-3.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| suse:curl | 8.14.1-150200.4.97.1 · SUSE:Linux Enterprise Micro 5.2 | Package registry (OSV) |
| suse:curl-mini | 8.14.1-160000.4.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- anonymous237 on hackeronefinder
- Daniel Stenbergremediation developer
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-9079176 days apartstale proxy password leak39Monitor
- CVE-2026-8926176 days apartpassword leak with netrc and user in URL36Monitor
- CVE-2026-6253125 days apartproxy credentials leak over redirect-to proxy23Monitor
- CVE-2026-378362 days aparttoken leak with redirect and netrc21Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-522 · Insufficiently Protected CredentialsCVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Session SidejackingCAPEC-102likelihood: High · High
- Signature Spoofing by Key TheftCAPEC-474likelihood: Medium · High
- Password Recovery ExploitationCAPEC-50likelihood: Medium · High
- KerberoastingCAPEC-509High
- Modify Existing ServiceCAPEC-551
- Remote Services with Stolen CredentialsCAPEC-555Very High
- Use of Known Domain CredentialsCAPEC-560likelihood: High · High
- Windows Admin Shares with Stolen CredentialsCAPEC-561
ATT&CK techniques
- Remote ServicesT1021
- Remote Services:SMB/Windows Admin SharesT1021.002
- Valid AccountsT1078
- Brute Force:Credential StuffingT1110.004
- Email Collection:Remote Email CollectionT1114.002
- External Remote ServicesT1133
- Create or Modify System ProcessT1543
- Use Alternate Authentication Material:Pass The HashT1550.002
- Use Alternate Authentication Material:Pass The TicketT1550.003
- Unsecured Credentials: Private KeysT1552.004
- Steal or Forge Kerberos TicketsT1558
- Steal or Forge Kerberos Tickets:KerberoastingT1558.003
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.