CVE-2025-61730 | Handshake messages may be processed at the incorrect encryption level in crypto/tls

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.

Published: 2026-01-28 Last update: 2026-02-03 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-61730 is rated Low Risk (21.5/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.01%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-61730

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-01-29 — 0.01% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-61730

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 1.4 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-61730

OS Trackers for CVE-2025-61730

vendor priority summary link
alpine — CVE-2025-61730: 1 source package rows (go); 90 state rows across 2 repos (3.23-community, edge-community); fixed 2, open 88. https://security.alpinelinux.org/vuln/CVE-2025-61730
debian not yet assigned CVE-2025-61730 not yet assigned priority: Debian including 4 source packages (golang-1.15, golang-1.19, golang-1.24, golang-1.25), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 3, resolved 2. https://security-tracker.debian.org/tracker/CVE-2025-61730
suse medium CVE-2025-61730 severity moderate: SUSE including 91 source package names (13.2-9.1:curl-8.6.0-5.1, 13.2-9.1:iputils-20221126-6.1, …), 509 product×package rows across 65 product lines (Container suse/sl-micro/6.0/baremetal-os-container, Container suse/sl-micro/6.0/base-os-container, … (65 product lines)): Fixed 439, Known Not Affected 56, First Fixed 14. https://www.suse.com/security/cve/CVE-2025-61730/
ubuntu medium CVE-2025-61730 medium priority: Ubuntu including 16 source packages (golang, golang-1.10, …), 82 status rows across 8 suites (bionic, focal, jammy, noble, questing, trusty, upstream, xenial): needs-triage 49, DNE 33. https://ubuntu.com/security/CVE-2025-61730

Affected software / configurations for CVE-2025-61730

Vendor Product Version Raw CPE
golang go < 1.24.12 cpe:2.3:a:golang:go:*:*:*:*:*:*:*:*
golang go >= 1.25.0, < 1.25.6 cpe:2.3:a:golang:go:*:*:*:*:*:*:*:*

References for CVE-2025-61730

cvelogic Threat Intelligence