Homepage

Improper Certificate Validation Affecting docker-dind-fips-29 package, versions <29.4.0-r4

Severity

 Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.01% (1st 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-MINIMOSLATEST-DOCKERDINDFIPS29-16087376
  • published16 Apr 2026
  • disclosed15 Apr 2026
Report a new vulnerability Found a mistake?

Introduced: 15 Apr 2026

NewCVE-2026-39984  (opens in a new tab)
CWE-295  (opens in a new tab)

How to fix?

Upgrade Minimos:latest docker-dind-fips-29 to version 29.4.0-r4 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream docker-dind-fips-29 package and not the docker-dind-fips-29 package as distributed by Minimos. See How to fix? for Minimos:latest 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.