Go standard library crypto-tls up to 1.25.11/1.26.4 TLS Handshake insertion of sensitive information into sent data
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 1.13 |
Summary
A vulnerability has been found in Go standard library crypto-tls up to 1.25.11/1.26.4 and classified as problematic. Affected is an unknown function of the component TLS Handshake. The manipulation leads to insertion of sensitive information into sent data. This vulnerability is referenced as CVE-2026-42505. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability was found in Go standard library crypto-tls up to 1.25.11/1.26.4 and classified as problematic. This issue affects an unknown part of the component TLS Handshake. The manipulation with an unknown input leads to a insertion of sensitive information into sent data vulnerability. Using CWE to declare the problem leads to CWE-201. The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor. Impacted is confidentiality. The summary by CVE is:
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.
The identification of this vulnerability is CVE-2026-42505 since 04/28/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
The vulnerability scanner Nessus provides a plugin with the ID 325629 (Linux Distros Unpatched Vulnerability : CVE-2026-42505), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 1.25.12, 1.26.5 or 1.27.0-rc.2 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (325629). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
- 1.25.0
- 1.25.1
- 1.25.2
- 1.25.3
- 1.25.4
- 1.25.5
- 1.25.6
- 1.25.7
- 1.25.8
- 1.25.9
- 1.25.10
- 1.25.11
- 1.26.0
- 1.26.1
- 1.26.2
- 1.26.3
- 1.26.4
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Insertion of sensitive information into sent dataCWE: CWE-201 / CWE-200 / CWE-284
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 325629
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2026-42505
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Upgrade: crypto-tls 1.25.12/1.26.5/1.27.0-rc.2
Timeline
04/28/2026 CVE reserved07/08/2026 Advisory disclosed
07/08/2026 VulDB entry created
07/08/2026 VulDB entry last update
Sources
Status: ConfirmedCVE: CVE-2026-42505 (🔒)
GCVE (CVE): GCVE-0-2026-42505
GCVE (VulDB): GCVE-100-376925
Entry
Created: 07/08/2026 18:47Updated: 07/08/2026 20:38
Changes: 07/08/2026 18:47 (53), 07/08/2026 18:55 (2), 07/08/2026 20:38 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.