Golang Go 1.26.0 Release Candidate 1
Approved changes feed: RSS · Atom
cpe:2.3:a:golang:go:1.26.0:rc1:*:*:*:*:*:*
part: a version: 1.26.0 update: rc1
| Vendor | Golang (670356c5-bd1b-5c66-9eee-f755f5cec4c7) |
|---|---|
| Product | Go (96a6ef33-04c7-5363-bbc8-7d2a06bf0b4b) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/golang/go |
purl2cpe | 2026-06-01 10:12:04.370762 |
pkg:golang/go/go |
purl2cpe | 2026-06-01 10:12:04.370764 |
pkg:googlesource/go |
purl2cpe | 2026-06-01 10:12:04.370765 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-68121 |
vulnerable | 2026-06-03 15:11:02.875985 |
Unexpected session resumption in crypto/tls
During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succeed when it should have failed. This may happen when a user calls Config.Clone and mutates the returned Config, or uses Config.GetConfigForClient. This can cause a client to resume a session with a server that it would not have resumed with during the initial handshake, or cause a server to resume a session with a client that it would not have resumed with during the initial handshake.
Published: 2026-02-05T17:48:44.141Z
Updated: 2026-04-29T13:29:25.582Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.