CVE-2026-32280 | Unexpected work during chain building in crypto/x509

During chain building, the amount of work that is done is not correctly limited when a large number of intermediate certificates are passed in VerifyOptions.Intermediates, which can lead to a denial of service. This affects both direct users of crypto/x509 and users of crypto/tls.

Published: 2026-04-08 Last update: 2026-04-16 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-32280 is rated Low Risk (30.2/100): CVSS High severity, with low exploitation likelihood (EPSS 0.01%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-32280

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-08 — 0.01% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-32280

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2026-32280

OS Trackers for CVE-2026-32280

vendor priority summary link
alpine — CVE-2026-32280: 1 source package rows (go); 100 state rows across 2 repos (3.23-community, edge-community); fixed 2, open 98. https://security.alpinelinux.org/vuln/CVE-2026-32280
debian not yet assigned CVE-2026-32280 not yet assigned priority: Debian including 5 source packages (golang-1.15, golang-1.19, golang-1.24, golang-1.25, golang-1.26), 7 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 3. https://security-tracker.debian.org/tracker/CVE-2026-32280
redhat high — https://access.redhat.com/security/cve/CVE-2026-32280
suse high CVE-2026-32280 severity important: SUSE including 17 source package names (go, go-doc, …), 106 product×package rows across 16 product lines (SUSE Linux Enterprise High Performance Computing 15 SP4-ESPOS, SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS, … (16 product lines)): Fixed 80, Known Not Affected 26. https://www.suse.com/security/cve/CVE-2026-32280/
ubuntu medium CVE-2026-32280 medium priority: Ubuntu including 16 source packages (golang, golang-1.10, …), 82 status rows across 8 suites (bionic, focal, jammy, noble, questing, trusty, upstream, xenial): needs-triage 49, DNE 33. https://ubuntu.com/security/CVE-2026-32280

Affected software / configurations for CVE-2026-32280

Vendor Product Version Raw CPE
golang go < 1.25.9 cpe:2.3:a:golang:go:*:*:*:*:*:*:*:*
golang go >= 1.26.0, < 1.26.2 cpe:2.3:a:golang:go:*:*:*:*:*:*:*:*

References for CVE-2026-32280

cvelogic Threat Intelligence