Improper Certificate Validation Affecting curl-minimal-debuginfo package, versions <0:8.21.0-5.amzn2023.0.1


Severity

Recommended
medium

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.41% (33rd 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-AMZN2023-CURLMINIMALDEBUGINFO-19818154
  • published15 Sept 2026
  • disclosed3 Jul 2026

Introduced: 3 Jul 2026

CVE-2026-9545  (opens in a new tab)
CWE-295  (opens in a new tab)

How to fix?

Upgrade Amazon-Linux:2023 curl-minimal-debuginfo to version 0:8.21.0-5.amzn2023.0.1 or higher.
This issue was patched in ALAS2023-2026-2132.

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl-minimal-debuginfo package and not the curl-minimal-debuginfo package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2023 relevant fixed versions and status.

In this scenario, libcurl first uses a proper HTTP/3 server for the initial transfers, and when it makes a second transfer to the same site it has been replaced by the attacker's impostor machine - without a valid certificate.

When libcurl returns to the hostname the second time with a cached SSL session (CURLOPT_SSL_SESSIONID_CACHE is not disabled) and early data enabled (the CURLSSLOPT_EARLYDATA bit is set in CURLOPT_SSL_OPTIONS), libcurl might send off the second request's bytes on that new connection before enforcing the certificate verification failure. Potentially leaking sensitive information.

CVSS Base Scores

version 3.1