Inefficient policy validation in crypto/x509

Answer in brief

CVE-2026-32281 records a Unknown severity vulnerability in Inefficient policy validation in crypto/x509. The current sources do not mark it as known exploited. The current feed maps stdlib (go). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Apr 7, 2026Updated Sep 1, 2026Source checked Sep 1, 2026First seen by HOL Aug 14, 2026Material review Sep 1, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps stdlib (go). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
stdlibgo	>=0 <1.25.9 >=1.26.0-0 <1.26.2	1.25.9, 1.26.2

Recommended response

Check inventory. Check lockfiles and deployed manifests for stdlib.
Review the reported fix. Update stdlib to 1.25.9 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Apr 7, 2026
Evidence: source:osv:source_dates:source-dates:record
Source modified
Sep 1, 2026
Evidence: source:osv:source_dates:source-dates:record
First seen by HOL
Aug 14, 2026

Sources and claim methodology

Upstream source description

Validating certificate chains which use policies is unexpectedly inefficient when certificates in the chain contain a very large number of policy mappings, possibly causing denial of service. This only affects validation of otherwise trusted certificate chains, issued by a root CA in the VerifyOptions.Roots CertPool, or in the system certificate pool.

Quoted source text, attributed separately from HOL analysis.