Improper Certificate Validation Affecting nerdctl-debuginfo package, versions <0:2.2.2-1.amzn2.0.1
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
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-AMZN2-NERDCTLDEBUGINFO-16341112
- published2 May 2026
- disclosed15 Apr 2026
Introduced: 15 Apr 2026
NewCVE-2026-39984 (opens in a new tab)How to fix?
Upgrade Amazon-Linux:2 nerdctl-debuginfo to version 0:2.2.2-1.amzn2.0.1 or higher.
This issue was patched in ALAS2-2026-3265.
NVD Description
Note: Versions mentioned in the description apply only to the upstream nerdctl-debuginfo package and not the nerdctl-debuginfo package as distributed by Amazon-Linux.
See How to fix? for Amazon-Linux:2 relevant fixed versions and status.
Sigstore Timestamp Authority is a service for issuing RFC 3161 timestamps. Versions 2.0.5 and below contain an authorization bypass vulnerability in the VerifyTimestampResponse function. VerifyTimestampResponse correctly verifies the certificate chain signature, but the TSA-specific constraint checks in VerifyLeafCert uses the first non-CA certificate from the PKCS#7 certificate bag instead of the leaf certificate from the verified chain. An attacker can exploit this by prepending a forged certificate to the certificate bag while the message is signed with an authorized key, causing the library to validate the signature against one certificate but perform authorization checks against another. This vulnerability only affects users of the timestamp-authority/v2/pkg/verification package and does not affect the timestamp-authority service itself or sigstore-go. The issue has been fixed in version 2.0.6.