crypto-x509 up to 1.25.8/1.26.1 on Go Certificate algorithmic complexity

Summaryinfo

A vulnerability has been found in crypto-x509 up to 1.25.8/1.26.1 on Go and classified as problematic. Affected is an unknown function of the component Certificate Handler. This manipulation causes algorithmic complexity. This vulnerability is handled as CVE-2026-32281. The attack can be initiated remotely. There is not any exploit available. The affected component should be upgraded.

Detailsinfo

A vulnerability has been found in crypto-x509 up to 1.25.8/1.26.1 on Go and classified as problematic. Affected by this vulnerability is an unknown part of the component Certificate Handler. The manipulation with an unknown input leads to a algorithmic complexity vulnerability. The CWE definition for the vulnerability is CWE-407. An algorithm in a product has an inefficient worst-case computational complexity that may be detrimental to system performance and can be triggered by an attacker, typically using crafted manipulations that ensure that the worst case is being reached. As an impact it is known to affect availability. The summary by CVE is:

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.

This vulnerability is known as CVE-2026-32281 since 03/11/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1499 for this issue.

Upgrading to version 1.25.9 or 1.26.2 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2026-1006). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

• Golang Go

Productinfo

Name

• crypto-x509

Version

• 1.25.0
• 1.25.1
• 1.25.2
• 1.25.3
• 1.25.4
• 1.25.5
• 1.25.6
• 1.25.7
• 1.25.8
• 1.26.0
• 1.26.1

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion