Skip to main content
VulnerabilityPublished Updated

CVE-2026-8926: 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

Affects curlSource GCVE Database

0
Compare

Not known to be exploited · CVSS 9.1 Critical · fixed in 8.14.1-2ubuntu1.4 : patch curl as a priority.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 8.14.1-2ubuntu1.4, 8.18.0-1ubuntu2.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Upgrade the Ubuntu curl to 8.14.1-2ubuntu1.4 (package) or 8.18.0-1ubuntu2.2 (package).

Affected software

ProductAffectedFixed in
Ubuntu 26.04 LTScurlpkg:deb/ubuntu/curl?arch=source&distro=resoluteOther threatsAffected
  • <8.18.0-1ubuntu2.2
Fixed in
  • 8.18.0-1ubuntu2.2
Ubuntu 25.10curlpkg:deb/ubuntu/curl?arch=source&distro=questingOther threatsAffected
  • <8.14.1-2ubuntu1.4
Fixed in
  • 8.14.1-2ubuntu1.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, avoid using .netrc files or embedding user credentials in URLs in affected environments.

Description

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.

References

Community reviews

Loading reviews…