golang.org/x/crypto vulnerable to auth bypass via unenforced @revoked status
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-42508US | — | — | ||
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. | ||||
02
references
External citations — patches, advisories, analysis.
- https://access.redhat.com/errata/RHSA-2026:23262WEB
- https://access.redhat.com/errata/RHSA-2026:23264WEB
- https://access.redhat.com/errata/RHSA-2026:26546WEB
- https://access.redhat.com/errata/RHSA-2026:26547WEB
- https://access.redhat.com/errata/RHSA-2026:35833WEB
- https://access.redhat.com/errata/RHSA-2026:36648WEB
- https://access.redhat.com/errata/RHSA-2026:36651WEB
- https://access.redhat.com/errata/RHSA-2026:36796WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan