Improper Certificate Validation Affecting curl-7.69.1 package, versions <7.69.1+e1


Severity

Recommended
0.0
high
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
15.14% (97th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ECHOLATEST-CURL7691-21280045
  • published20 Oct 2026
  • disclosed5 Aug 2021

Introduced: 5 Aug 2021

CVE-2021-22926  (opens in a new tab)
CWE-295  (opens in a new tab)

How to fix?

Upgrade Echo:latest curl-7.69.1 to version 7.69.1+e1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl-7.69.1 package and not the curl-7.69.1 package as distributed by Echo. See How to fix? for Echo:latest relevant fixed versions and status.

libcurl-using applications can ask for a specific client certificate to be used in a transfer. This is done with the CURLOPT_SSLCERT option (--cert with the command line tool).When libcurl is built to use the macOS native TLS library Secure Transport, an application can ask for the client certificate by name or with a file name - using the same option. If the name exists as a file, it will be used instead of by name.If the appliction runs with a current working directory that is writable by other users (like /tmp), a malicious user can create a file name with the same name as the app wants to use by name, and thereby trick the application to use the file based cert instead of the one referred to by name making libcurl send the wrong client certificate in the TLS connection handshake.

References

CVSS Base Scores

version 3.1