CVE-2026-42508
Previously, a revoked 'SignatureKey' belonging to a CA was not …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- go.dev/cl/781220
- go.dev/issue/79568
- groups.google.com/g/golang-announce/c/a082jnz-LvI
- pkg.go.dev/vuln/GO-2026-5021
- nvd.nist.gov/vuln/detail/CVE-2026-42508
- github.com/advisories/GHSA-5cgq-3rg8-m6cv
- access.redhat.com/errata/RHSA-2026:23262
- access.redhat.com/errata/RHSA-2026:23264
- nvd.nist.gov/vuln/detail/CVE-2026-42508
- cve.org/CVERecord?id=CVE-2026-42508
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.