Skip to main content
VulnerabilityPublished Updated

CVE-2026-32283: Go standard library crypto/tls · Improper Locking

Affects Go standard library crypto/tlsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 1.26.2 or 1.25.9 soon.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.26.2, 1.25.9
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade Go standard library crypto/tls to 1.26.2 or 1.25.9.

Affected software

ProductAffectedFixed in
Go standard librarycrypto/tlsAffected
  • >=1.26.0-0 <1.26.2
Fixed in
  • 1.26.2
Go standard librarycrypto/tlsAffected
  • <1.25.9
Fixed in
  • 1.25.9
Gocrypto/tlspkg:golang/crypto/tlsOther threatsAffected
  • <1.25.9
  • >=1.26.0-0 <1.26.2
Fixed in
  • 1.25.9
  • 1.26.2
Gogithub.com/golang/go/src/crypto/tlspkg:golang/github.com/golang/go/src/crypto/tlsOther threatsAffected
  • =0
  • =1.26.0-0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available. Red Hat has released security updates for affected products including Red Hat Ansible Automation Platform 2.6 and related components. Users should apply the provided patches or upgrade to fixed versions as per the vendor advisories. No additional mitigations are specified or required beyond applying the official fixes.

Description

If one side of the TLS connection sends multiple key update messages post-handshake in a single record, the connection can deadlock, causing uncontrolled consumption of resources. This can lead to a denial of service. This only affects TLS 1.3.

References

Community reviews

Loading reviews…