Loading vulnerability…
CVE-2025-61730 is a TLS 1.3 handshake-processing flaw in Go's crypto/tls package. When multiple handshake messages are contained in TLS records spanning an encryption-level transition, subsequent messages can be processed before the implementation changes to the required encryption level. This violates TLS 1.3 requirements that handshake messages must not span key changes. An attacker may cause handshake content that should have been protected at a later encryption level to be processed at an earlier level, potentially including plaintext processing of content expected to be encrypted.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
28 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Go vulnerability described as functionally the same TLS 1.3 wrong-encryption-level handshake-message acceptance issue as the Rustls advisory.
A Go crypto/tls TLS 1.3 handshake state-handling flaw that can cause minor information disclosure when a network-local attacker injects handshake messages spanning encryption-level boundaries.
Go crypto/tls handshake processing flaw where messages spanning encryption boundaries could be handled at incorrect encryption levels, potentially exposing information to attackers with network-local visibility.
An information disclosure issue in Go’s crypto/tls where certain handshake messages may be processed at an incorrect encryption level, potentially leaking information when attackers inject packets.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.