CVE-2026-42505: Invoking Encrypted Client Hello privacy leak in crypto/tls
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.38% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: Go standard library crypto/tls 1.25.12, 1.26.5, 1.27.0-rc.2; azl3 golang 1.26.4-3 on Azure Linux 3.0 1.26.5-2.
Low priority for now. Upgrade to Go standard library crypto/tls 1.25.12, 1.26.5, 1.27.0-rc.2; azl3 golang 1.26.4-3 on Azure Linux 3.0 1.26.5-2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- BDU:2026-15912
- ALSA-2026:37435
- ALSA-2026:37436
- ALSA-2026:38995
- ALSA-2026:66364
- GO-2026-5856
- openSUSE-SU-2026:11212-1
- openSUSE-SU-2026:11216-1
- openSUSE-SU-2026:11232-1
- openSUSE-SU-2026:11471-1
- openSUSE-SU-2026:11798-1
- openSUSE-SU-2026:21321-1
- openSUSE-SU-2026:21324-1
- openSUSE-SU-2026:21341-1
- RHSA-2026:36477
- RHSA-2026:36510
- RHSA-2026:37435
- RHSA-2026:37436
- RHSA-2026:38995
- RHSA-2026:66364
- Published
- Jul 8, 2026
- Updated
- Oct 25, 2026
- EPSS
- 0.3% · 32th percentile
- CWE
- CWE-201
Report tools
Action score
21
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| golang | go | cpe:2.3:a:golang:go |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Go). Independent of NVD's CPE analysis and usually ahead of it.
Go standard library crypto/tls
- before 1.25.12affected · semver
- 1.26.0-0 and later · before 1.26.5affected · semver
- 1.27.0-0 and later · before 1.27.0-rc.2affected · semver
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- golang go1.23.0 and later · before 1.25.12
- golang go1.26.0 and later · before 1.26.5
- golang go1.27
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | go-toolset | before 1.26.5-1.el10_2.alma.1 | 1.26.5-1.el10_2.alma.1 |
| AlmaLinux:10 | golang | before 1.26.5-1.el10_2.alma.1 | 1.26.5-1.el10_2.alma.1 |
| AlmaLinux:10 | golang-bin | before 1.26.5-1.el10_2.alma.1 | 1.26.5-1.el10_2.alma.1 |
| AlmaLinux:10 | golang-docs | before 1.26.5-1.el10_2.alma.1 | 1.26.5-1.el10_2.alma.1 |
| AlmaLinux:10 | golang-misc | before 1.26.5-1.el10_2.alma.1 | 1.26.5-1.el10_2.alma.1 |
| AlmaLinux:10 | golang-race | before 1.26.5-1.el10_2.alma.1 | 1.26.5-1.el10_2.alma.1 |
| AlmaLinux:10 | golang-src | before 1.26.5-1.el10_2.alma.1 | 1.26.5-1.el10_2.alma.1 |
| AlmaLinux:10 | golang-tests | before 1.26.5-1.el10_2.alma.1 | 1.26.5-1.el10_2.alma.1 |
| AlmaLinux:8 | delve | before 1.26.1-1.module_el8.10.0+4223+bd807c2e | 1.26.1-1.module_el8.10.0+4223+bd807c2e |
| AlmaLinux:8 | go-toolset | before 1.26.5-1.module_el8.10.0+4223+bd807c2e | 1.26.5-1.module_el8.10.0+4223+bd807c2e |
| AlmaLinux:8 | golang | before 1.26.5-1.module_el8.10.0+4223+bd807c2e | 1.26.5-1.module_el8.10.0+4223+bd807c2e |
| AlmaLinux:8 | golang-bin | before 1.26.5-1.module_el8.10.0+4223+bd807c2e | 1.26.5-1.module_el8.10.0+4223+bd807c2e |
| AlmaLinux:8 | golang-docs | before 1.26.5-1.module_el8.10.0+4223+bd807c2e | 1.26.5-1.module_el8.10.0+4223+bd807c2e |
| AlmaLinux:8 | golang-misc | before 1.26.5-1.module_el8.10.0+4223+bd807c2e | 1.26.5-1.module_el8.10.0+4223+bd807c2e |
| AlmaLinux:8 | golang-race | before 1.26.5-1.module_el8.10.0+4223+bd807c2e | 1.26.5-1.module_el8.10.0+4223+bd807c2e |
| AlmaLinux:8 | golang-src | before 1.26.5-1.module_el8.10.0+4223+bd807c2e | 1.26.5-1.module_el8.10.0+4223+bd807c2e |
| AlmaLinux:8 | golang-tests | before 1.26.5-1.module_el8.10.0+4223+bd807c2e | 1.26.5-1.module_el8.10.0+4223+bd807c2e |
| AlmaLinux:9 | git-lfs | before 3.7.1-4.el9_8.3 | 3.7.1-4.el9_8.3 |
| AlmaLinux:9 | go-toolset | before 1.26.5-1.el9_8 | 1.26.5-1.el9_8 |
| AlmaLinux:9 | golang | before 1.26.5-1.el9_8 | 1.26.5-1.el9_8 |
| AlmaLinux:9 | golang-bin | before 1.26.5-1.el9_8 | 1.26.5-1.el9_8 |
| AlmaLinux:9 | golang-docs | before 1.26.5-1.el9_8 | 1.26.5-1.el9_8 |
| AlmaLinux:9 | golang-misc | before 1.26.5-1.el9_8 | 1.26.5-1.el9_8 |
| AlmaLinux:9 | golang-race | before 1.26.5-1.el9_8 | 1.26.5-1.el9_8 |
+26
Same product
golang: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-7187The "go get" implementation in Go 1.9.4, when the -insecure command-line option is used, does not validate the import path (get/vcs.go only…54Plan
- CVE-2018-16873In Go before 1.10.6 and 1.11.x before 1.11.3, the "go get" command is vulnerable to remote code execution when executed with the -u flag…52Plan
- CVE-2021-38297Go before 1.16.9 and 1.17.x before 1.17.2 has a Buffer Overflow via large arguments in a function invocation from a WASM module, when…42Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-42499May 7, 2026 · Quadratic string concatenation in consumePhrase in net/mail30Monitor
- ← EarlierCVE-2026-42501May 7, 2026 · Malicious module proxy can bypass checksum database in cmd/go30Monitor
- ← EarlierCVE-2026-39822Jul 8, 2026 · Root escape via symlink plus trailing slash in os31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Go standard library crypto/tls | 1.25.12 | Vendor (CNA) |
| Go standard library crypto/tls | 1.26.5 | Vendor (CNA) |
| Go standard library crypto/tls | 1.27.0-rc.2 | Vendor (CNA) |
| azl3 golang 1.26.4-3 on Azure Linux 3.0 | 1.26.5-2 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:delve | 1.26.1-1.module_el8.10.0+4223+bd807c2e · AlmaLinux:8 | Package registry (OSV) |
| almalinux:git-lfs | 3.7.1-4.el9_8.3 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:go-toolset | 1.26.5-1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:golang | 1.26.5-1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:golang-bin | 1.26.5-1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:golang-docs | 1.26.5-1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:golang-misc | 1.26.5-1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:golang-race | 1.26.5-1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:golang-src | 1.26.5-1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:golang-tests | 1.26.5-1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| alpine:go | 1.26.8-r0 · Alpine:v3.24 | Package registry (OSV) |
| debian:golang-1.25 | 1.25.12-1 · Debian:14 | Package registry (OSV) |
| debian:golang-1.26 | 1.26.5-1 · Debian:14 | Package registry (OSV) |
| debian:golang-1.27 | 1.27~rc2-1 · Debian:14 | Package registry (OSV) |
| Go:stdlib | 1.25.12 | Package registry (OSV) |
| Go:stdlib | 1.26.5 | Package registry (OSV) |
| Go:stdlib | 1.27.0-rc.2 | Package registry (OSV) |
| opensuse:go-passbolt-cli | 0.5.2-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:go1.25 | 1.25.12-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:go1.26 | 1.26.5-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:go1.26-openssl | 1.26.5-160000.1.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:mihomo | 1.19.28-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:tekton-cli | 0.46.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:go-toolset | 0:1.26.5-1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:golang | 0:1.26.5-1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:golang-bin | 0:1.26.5-1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
+21
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-201 · Insertion of Sensitive Information Into Sent DataCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Choosing Message IdentifierCAPEC-12likelihood: High · High
- Exploiting Incorrectly Configured SSL/TLSCAPEC-217likelihood: Low
- WiFi MAC Address TrackingCAPEC-612Low
- WiFi SSID TrackingCAPEC-613Low
- Cellular Broadcast Message RequestCAPEC-618Low
- Signal Strength TrackingCAPEC-619Low
- Analysis of Packet Timing and SizesCAPEC-621Low
- Electromagnetic Side-Channel AttackCAPEC-622Low
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.