password leak with netrc and user in URL
Noroxi assessment
Priority: Monitor (action score 36/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.44% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: curl curl 4ae1d7cc2643e4773a136395f12bc02fc6867854, 8.14.2, 8.16.1; azl3 curl 8.11.1-9 on Azure Linux 3.0 8.11.1-10.
Low priority for now. Upgrade to curl curl 4ae1d7cc2643e4773a136395f12bc02fc6867854, 8.14.2, 8.16.1; azl3 curl 8.11.1-9 on Azure Linux 3.0 8.11.1-10 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 asking curl to use a `.netrc` file to find credentials and at the same time specifying a URL with a username (without a password), like `https://user@example.com/`, curl could wrongly get and use the password for *another* user set in the `.netrc` file for that host if such a one exists and there is no match for the specified user.
- EUVD-2026-41507
- ALSA-2026:69125
- openSUSE-SU-2026:11230-1
- openSUSE-SU-2026:21774-1
- RHSA-2026:29017
- RHSA-2026:34975
- RHSA-2026:69125
- RHSA-2026:72506
- RLSA-2026:69125
- SUSE-SU-2026:23350-1
- SUSE-SU-2026:23361-1
- SUSE-SU-2026:23498-1
- SUSE-SU-2026:23638-1
- SUSE-SU-2026:3798-1
- SUSE-SU-2026:3958-1
- SUSE-SU-2026:4047-1
- Published
- Jul 3, 2026
- Updated
- Sep 15, 2026
- EPSS
- 0.4% · 37th percentile
- CWE
- CWE-522
Report tools
Action score
36
Monitor
Low priority for now.
- CVSS
- 36 / 40 · 9.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- total
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 curl8.11.1 and later · before 8.21.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.20.0, 8.19.0, 8.18.0, 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.1affected
- 8.11.1 and later · before 8.14.2affected · semver
- 8.15.0 and later · before 8.16.1affected · semver
- 8.17.0 and later · before 8.20.1affected · semver
- e9b9bbac22c26cf67316fa8e6c6b9e831af31949 and later · before 4ae1d7cc2643e4773a136395f12bc02fc6867854affected · git
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | curl | before 8.12.1-4.el10_2.6 | 8.12.1-4.el10_2.6 |
| AlmaLinux:10 | libcurl | before 8.12.1-4.el10_2.6 | 8.12.1-4.el10_2.6 |
| AlmaLinux:10 | libcurl-devel | before 8.12.1-4.el10_2.6 | 8.12.1-4.el10_2.6 |
| AlmaLinux:10 | libcurl-minimal | before 8.12.1-4.el10_2.6 | 8.12.1-4.el10_2.6 |
| Alpine:v3.23 | curl | from 8.11.1 · before 8.22.0-r0 | 8.22.0-r0 |
| Alpine:v3.24 | curl | from 8.11.1 · before 8.21.0-r0 | 8.21.0-r0 |
| Debian:13 | curl | from 0 | — |
| Debian:14 | curl | before 8.21.0~rc2-1 | 8.21.0~rc2-1 |
| openSUSE:Leap 16.0 | curl | before 8.14.1-160000.9.1 | 8.14.1-160000.9.1 |
| openSUSE:Tumbleweed | curl | before 8.21.0-1.1 | 8.21.0-1.1 |
| Red Hat:enterprise_linux_eus:10.0 | curl | before 0:8.12.1-1.el10_0.10 | 0:8.12.1-1.el10_0.10 |
| Red Hat:enterprise_linux_eus:10.0 | curl-debuginfo | before 0:8.12.1-1.el10_0.10 | 0:8.12.1-1.el10_0.10 |
| Red Hat:enterprise_linux_eus:10.0 | curl-debugsource | before 0:8.12.1-1.el10_0.10 | 0:8.12.1-1.el10_0.10 |
| Red Hat:enterprise_linux_eus:10.0 | libcurl | before 0:8.12.1-1.el10_0.10 | 0:8.12.1-1.el10_0.10 |
| Red Hat:enterprise_linux_eus:10.0 | libcurl-debuginfo | before 0:8.12.1-1.el10_0.10 | 0:8.12.1-1.el10_0.10 |
| Red Hat:enterprise_linux_eus:10.0 | libcurl-devel | before 0:8.12.1-1.el10_0.10 | 0:8.12.1-1.el10_0.10 |
| Red Hat:enterprise_linux_eus:10.0 | libcurl-minimal | before 0:8.12.1-1.el10_0.10 | 0:8.12.1-1.el10_0.10 |
| Red Hat:enterprise_linux_eus:10.0 | libcurl-minimal-debuginfo | before 0:8.12.1-1.el10_0.10 | 0:8.12.1-1.el10_0.10 |
| Red Hat:enterprise_linux:10.2 | curl | before 0:8.12.1-4.el10_2.6 | 0:8.12.1-4.el10_2.6 |
| Red Hat:enterprise_linux:10.2 | curl-debuginfo | before 0:8.12.1-4.el10_2.6 | 0:8.12.1-4.el10_2.6 |
| Red Hat:enterprise_linux:10.2 | curl-debugsource | before 0:8.12.1-4.el10_2.6 | 0:8.12.1-4.el10_2.6 |
| Red Hat:enterprise_linux:10.2 | libcurl | before 0:8.12.1-4.el10_2.6 | 0:8.12.1-4.el10_2.6 |
| Red Hat:enterprise_linux:10.2 | libcurl-debuginfo | before 0:8.12.1-4.el10_2.6 | 0:8.12.1-4.el10_2.6 |
| Red Hat:enterprise_linux:10.2 | libcurl-devel | before 0:8.12.1-4.el10_2.6 | 0:8.12.1-4.el10_2.6 |
+33
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-2026-8924Jul 3, 2026 · trailing dot domain super cookie36Monitor
- ← EarlierCVE-2026-8925Jul 3, 2026 · The curl logic that works with SASL authentication could end up cleaning up
the GSASL context *twice* without clearing the pointer in betwee39Monitor
- Later →CVE-2026-8927Jul 3, 2026 · env-set cross-proxy Digest auth state leak36Monitor
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 | 4ae1d7cc2643e4773a136395f12bc02fc6867854 | Vendor (CNA) |
| curl curl | 8.14.2 | Vendor (CNA) |
| curl curl | 8.16.1 | Vendor (CNA) |
| curl curl | 8.20.1 | Vendor (CNA) |
| azl3 curl 8.11.1-9 on Azure Linux 3.0 | 8.11.1-10 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:curl | 8.12.1-4.el10_2.6 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:libcurl | 8.12.1-4.el10_2.6 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:libcurl-devel | 8.12.1-4.el10_2.6 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:libcurl-minimal | 8.12.1-4.el10_2.6 · AlmaLinux:10 | Package registry (OSV) |
| alpine:curl | 8.22.0-r0 · Alpine:v3.23 | Package registry (OSV) |
| debian:curl | 8.21.0~rc2-1 · Debian:14 | Package registry (OSV) |
| opensuse:curl | 8.21.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:cargo | 0:1.96.1-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:clippy | 0:1.96.1-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:curl | 0:8.21.0-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:curl-debuginfo | 0:8.12.1-4.el10_2.6 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:curl-debugsource | 0:8.12.1-4.el10_2.6 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:libcurl | 0:8.12.1-4.el10_2.6 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:libcurl | 0:8.21.0-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:libcurl-debuginfo | 0:8.12.1-4.el10_2.6 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:libcurl-devel | 0:8.12.1-4.el10_2.6 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:libcurl-devel | 0:8.21.0-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:libcurl-minimal | 0:8.12.1-4.el10_2.6 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:libcurl-minimal | 0:8.21.0-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:libcurl-minimal-debuginfo | 0:8.12.1-4.el10_2.6 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:rust | 0:1.96.1-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:rust-analyzer | 0:1.96.1-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:rust-debugger-common | 0:1.96.1-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:rust-doc | 0:1.96.1-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:rust-gdb | 0:1.96.1-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
+4
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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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.
- Stefan Eissingremediation developer
- Joshua Rogers (Aisle Research)finder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-90790 days apartstale proxy password leak39Monitor
- CVE-2026-625351 days apartproxy credentials leak over redirect-to proxy23Monitor
- CVE-2026-3783114 days aparttoken leak with redirect and netrc21Monitor
- CVE-2025-14524176 days apartbearer token leak on cross-protocol redirect21Monitor
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.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-522 · Insufficiently Protected CredentialsCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.