Secuno
ENNL
Book demo

CVE-2026-42508

Golang Crypto vulnerability

9.1 CRITICALEPSS 0.65%
  1. Published22 May 2026

Description

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.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityNone
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected products

Golang Crypto< 0.52.0

Remediation

Fixed in
Golang Crypto≥ 0.52.0
Patch & vendor advisories

References

and 39 more references

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-1093998.1
SWUpdate through 2026.05.1 contains an improper certificate validation vulnerability in…
CVE-2026-9620710.0
Improper certificate validation in Microsoft Partner Center allows an unauthorized…
CVE-2026-952109.1
Improper certificate validation in gnutls v3.8.13 causes the application to accept…
CVE-2026-672708.2
Dell Container Storage Modules (CSM) versions prior to 1.18.0, contains an Improper…
CVE-2026-861319.8
A code injection vulnerability in WatchGuard Fireware OS's BOVPN Over TLS client…
CVE-2026-933028.2
MatchTrustedPeer ignores the public key used, leading to forged CA clones passing…

Frequently asked

Is CVE-2026-42508 being actively exploited?

CVE-2026-42508 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.65%.

How severe is CVE-2026-42508?

CVE-2026-42508 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 0.65% probability of exploitation.

Which products are affected by CVE-2026-42508?

Affected products include Golang Crypto.

How do I fix CVE-2026-42508?

Upgrade affected software to a fixed version, for example Golang Crypto 0.52.0 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-42508 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.