ZeroDay Findings
Sign inSign up

Findings

CVE-2026-42508

Previously, a revoked 'SignatureKey' belonging to a CA was not correctly checked for revocation.

Published May 22, 2026 · updated Sep 15, 2026 · golang crypto

Previously, a revoked 'SignatureKey' belonging to a CA was not correctly checked for revocation. Now, both the 'key' and 'key.SignatureKey' are checked for @revoked.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. May 22, 2026 · NIST NVD

    Detected

    Previously, a revoked 'SignatureKey' belonging to a CA was not correctly checked for revocation. Now, both the 'key' and 'key.SignatureKey' are checked for @revoked.

  2. Sep 15, 2026 · NIST NVD

    Updated

    Previously, a revoked 'SignatureKey' belonging to a CA was not correctly checked for revocation. Now, both the 'key' and 'key.SignatureKey' are checked for @revoked.

Affected

  • cpe golang/cryptoversion unspecified

Sources

  • CVE.orgVulnerability recordCVE-2026-42508

    Official CVE identifier

    cve.org
  • NIST NVDVulnerability recordCVE-2026-42508

    Previously, a revoked 'SignatureKey' belonging to a CA was not correctly checked for revocation. Now, both the 'key' and 'key.SignatureKey' are checked for @revoked.

    nvd.nist.gov

References

CVE-2026-42508 · ZeroDay Findings