CyberSecBulletin
CVE-2026-94266NVD status: Awaiting Analysis

curl: Insufficiently Protected Credentials

CVE-2026-94266 is a high-severity insufficiently protected credentials vulnerability in curl, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected curl versions: 8.22.0 and earlier; 8.21.0 and earlier; 8.20.0 and earlier, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.56% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Check which version of curl you run against the affected versions below, and install the vendor's latest release.
  2. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
Curlcurl8.22.0 and earlier; 8.21.0 and earlier; 8.20.0 and earlier; 8.19.0 and earlier; 8.18.0 and earlier; 8.17.0 and earlier; 8.16.0 and earlier; 8.15.0 and earlier; and 32 more rangesNot stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
NoneNothing can be modified.
Availability
NoneAvailability is not affected.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. Scored by CISA (ADP).

Official description

libcurl could accidentally return a URL for `curl_easy_getinfo()`'s `CURLINFO_EFFECTIVE_URL` option containing credentials, even though neither the URL provided to libcurl nor the redirected URL did.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Insufficiently Protected Credentials

The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.

How developers prevent this class of flaw

  • Use an appropriate security mechanism to protect the credentials.
  • Make appropriate use of cryptography to protect the credentials.
  • Use industry standards to protect the credentials (e.g. LDAP, keystore, etc.).

More Insufficiently Protected Credentials vulnerabilities (CWE-522)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: poc, automatable: yes, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in curl

All curl vulnerabilities

Recent Insufficiently Protected Credentials vulnerabilities

Spotted an error? Tell us.