CVE-2025-61730

CVE-2025-61730 is a medium-severity vulnerability in Golang Go with a CVSS 3.x base score of 5.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Description

During the TLS 1.3 handshake if multiple messages are sent in records that span encryption level boundaries (for instance the Client Hello and Encrypted Extensions messages), the subsequent messages may be processed before the encryption level changes. This can cause some minor information disclosure if a network-local attacker can inject messages during the handshake.

Frequently asked questions

What is CVE-2025-61730?
During the TLS 1.3 handshake if multiple messages are sent in records that span encryption level boundaries (for instance the Client Hello and Encrypted Extensions messages), the subsequent messages may be processed before the encryption level changes. This can cause some minor information disclosure if a network-local attacker can inject messages during the handshake.
How severe is CVE-2025-61730?
CVE-2025-61730 has a CVSS 3.x base score of 5.3, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.
Is CVE-2025-61730 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (19th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-61730?
CVE-2025-61730 affects Golang Go. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-61730?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-61730 have an EU (EUVD) identifier?
Yes. CVE-2025-61730 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-206448.
When was CVE-2025-61730 published?
CVE-2025-61730 was published on 2026-01-28 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Golang Go

All CVEs affecting Golang Go →