Go standard library · Go · published 2026-07-08

CVE-2026-42505Invoking Encrypted Client Hello privacy leak in crypto/tls

Routine No exploitation evidence; EPSS 0.4%.

CVE-2026-42505 is not known to be exploited in the wild. EPSS estimates a 0.4% chance of exploitation in the next 30 days, higher than 33% of all CVEs. This Go vulnerability: CVSS 5.3 (v3.1), attacks can be automated. Fixed upstream in Go 1.26.5, 1.25.12. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Go 1.26.5, 1.25.12.

Patch events

  1. This monthSecurity release

    Language runtimeGo

    Go security releases: 1.26.5, 1.25.12

    Upgrade to 1.26.51.25.12

    Why: Vendor security release for server software (most severe: CVE-2026-39822).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.4% (33th pct)FIRST EPSS v2026.06.15
CVSS base score5.3 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableYesCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

Handshakes which used Encrypted Client Hello could be de-anonymized by a passive network observer due to a disclosure of pre-shared key identities in the unencrypted client hello.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →