Skip to main content
Mallory
MediumVulnerability

CVE-2025-61730: TLS 1.3 Handshake Encryption-Level Confusion in Go

Published Jan 28, 2026 · Updated 11 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS5.3Medium · v3.1
EPSS0.32%26th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Golang
IdentifiersCVE-2025-61730CWE-696

CVE-2025-61730 is a TLS 1.3 handshake-processing vulnerability in Go's crypto/tls standard library package. When multiple handshake messages are carried in records spanning encryption-level boundaries, subsequent messages may be processed before the corresponding encryption-level transition occurs. A network-local attacker capable of injecting messages during the handshake may exploit this incorrect processing order to cause limited information disclosure. Affected releases include Go versions before 1.24.12 and Go 1.25.0 through 1.25.5. Affected entry points include TLS handshake, connection read/write, dialing, and QUIC handshake interfaces.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can cause minor information disclosure during a TLS 1.3 handshake. The specific information exposed is not established. Arbitrary code execution, privilege escalation, and integrity or availability impacts are not established for this vulnerability.

Mitigation

If you can’t patch tonight, do this now.

No vulnerability-specific workaround is documented. Network segmentation and restricting connectivity to trusted peers may reduce opportunities for network-local message injection, but do not correct the handshake-processing defect.

Remediation

Patch, then assume compromise.

Upgrade to Go 1.24.12 or Go 1.25.6, or a later supported release containing the fix. Rebuild and redeploy applications using the affected standard library; updating the installed toolchain alone does not update previously compiled binaries. For vendor-packaged applications and appliances, install a vendor release that incorporates the corrected Go library.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GolangGoapplication
FAQ

Frequently asked questions

Is CVE-2025-61730 exploited in the wild?
As of Nov 7, 2026, Mallory has no reports of CVE-2025-61730 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-61730?
As of Nov 7, 2026, Mallory has found no public exploit for CVE-2025-61730.
Is there a patch for CVE-2025-61730?
Upgrade to Go 1.24.12 or Go 1.25.6, or a later supported release containing the fix. Rebuild and redeploy applications using the affected standard library; updating the installed toolchain alone does not update previously compiled binaries.
What products are affected by CVE-2025-61730?
Golang Go.
How severe is CVE-2025-61730?
CVE-2025-61730 has a CVSS v3.1 score of 5.3 (Medium) and an EPSS score of 0.32% (26th percentile) as of Nov 7, 2026.
Activity feed

Recent activity

33 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+3 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity14Community discussion across Reddit, Mastodon, and other social sources.