Loading story…
Go disclosed CVE-2025-61730 (GO-2026-4340), a flaw in the crypto/tls implementation's handling of TLS 1.3 handshake records. When multiple handshake messages cross encryption-level boundaries within TLS records, Go can process later messages before updating the active encryption level.
A network-local attacker able to inject messages during a TLS handshake could exploit the condition to obtain minor information disclosure. Organizations using affected Go applications should upgrade to Go 1.24.12 or later, or 1.25.6 or later; releases before 1.24.12 and versions from 1.25.0 through 1.25.5 are affected.
See affected versions and whether adversaries are exploiting it.
2 events from the most recent confirmed update back to the earliest known activity.
Go disclosed GO-2026-4340 (CVE-2025-61730), affecting TLS 1.3 handshake processing in crypto/tls. A network-local attacker able to inject handshake messages could cause minor information disclosure; releases before Go 1.24.12 and Go 1.25.0 through before 1.25.6 are affected.
The Go project tracked an issue in crypto/tls where TLS 1.3 initial handshake records spanning encryption-level boundaries could cause subsequent handshake messages to be processed before the encryption level changed. The issue was credited to Coia Prant (github.com/rbqvq).
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Go disclosed **CVE-2026-32283**, an Important denial-of-service flaw in `crypto/tls` that can deadlock TLS 1.3 connections when a peer sends multiple post-handshake key update messages in a single record, leading to uncontrolled resource consumption. Go also disclosed **CVE-2026-27144** in `cmd/compile`, where a no-op interface conversion could bypass overlap checks for memory moves, creating conditions for unsafe overlapping copies and possible memory corruption or unexpected behavior at runtime. Red Hat subsequently shipped fixes for these Go flaws across multiple RHEL 8, 9, and 10 channels and dependent packages including **golang**, **rhc**, **ipp-usb**, **gvisor-tap-vsock**, and **Cryostat 4**, often alongside other Go vulnerabilities in `crypto/x509` and `internal/syscall/unix`. Advisories rated the updates **Important**, with `CVE-2026-32283` scored **CVSS 7.5** by Red Hat, and updated package builds were released for major architectures including `x86_64`, `aarch64`, `ppc64le`, and `s390x` across standard, EUS, AUS, SAP, and Extended Life Cycle offerings.
Aug 20, 2026
A denial-of-service vulnerability tracked as **CVE-2026-32280** was disclosed in Go's standard library, affecting `crypto/x509` and `crypto/tls` during X.509 certificate verification. The flaw stems from excessive certificate chain-building work in `Verify` when an attacker supplies a large number of candidate intermediate certificates, causing uncontrolled CPU and resource consumption and potentially making applications unavailable. The issue affects systems that use Go to process untrusted TLS certificates or X.509 chains, particularly network-facing services that accept attacker-controlled certificate inputs. Red Hat rated the vulnerability **Important** with a **CVSS v3.1 score of 7.5**, mapped it to **CWE-770**, and published fixes across multiple products, including **Red Hat Enterprise Linux 10 golang** and several **Ansible Automation Platform**, **Cryostat**, and **HawtIO** components.
Aug 20, 2026
Rustls has fixed a medium-severity TLS 1.3 protocol-handling flaw, tracked as `RUSTSEC-2026-0285` and `GHSA-2mjx-qc3c-rqvc`, that accepted handshake messages crossing encryption-level boundaries if they followed a key-changing message in the same TLS record. This could allow, for example, an unencrypted `EncryptedExtensions` message to be accepted alongside `ServerHello`, contrary to RFC 8446 section 5.1. The issue affects Rustls releases from `0.23.13` through versions before `0.23.45`; versions earlier than `0.23.13` are unaffected. Rustls `0.23.45` remediates the defect. A network-position attacker cannot alter or complete the authenticated handshake because transcript authentication remains intact, but a peer could send handshake content in plaintext when it should have been encrypted without the connection being rejected. OpenSSL and BoringSSL are not affected; the flaw is functionally equivalent to Go advisory `GO-2026-4340` / `CVE-2025-61730`.
Sep 14, 2026