{"resultsPerPage":1,"startIndex":0,"totalResults":1,"format":"NVD_CVE","version":"2.0","timestamp":"2026-06-05T00:31:22.801","vulnerabilities":[{"cve":{"id":"CVE-2025-68121","sourceIdentifier":"security@golang.org","published":"2026-02-05T18:16:10.857","lastModified":"2026-04-29T14:16:16.170","vulnStatus":"Modified","cveTags":[],"descriptions":[{"lang":"en","value":"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."},{"lang":"es","value":"Durante la reanudación de la sesión en crypto/tls, si la Config subyacente tiene sus campos ClientCAs o RootCAs mutados entre el handshake inicial y el handshake reanudado, el handshake reanudado puede tener éxito cuando debería haber fallado. Esto puede ocurrir cuando un usuario llama a Config.Clone y muta la Config devuelta, o usa Config.GetConfigForClient. Esto puede hacer que un cliente reanude una sesión con un servidor con el que no la habría reanudado durante el handshake inicial, o hacer que un servidor reanude una sesión con un cliente con el que no la habría reanudado durante el handshake inicial."}],"metrics":{"cvssMetricV31":[{"source":"nvd@nist.gov","type":"Primary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","baseScore":10.0,"baseSeverity":"CRITICAL","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"CHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"},"exploitabilityScore":3.9,"impactScore":6.0},{"source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","baseScore":9.1,"baseSeverity":"CRITICAL","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"NONE"},"exploitabilityScore":3.9,"impactScore":5.2}]},"weaknesses":[{"source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","type":"Secondary","description":[{"lang":"en","value":"CWE-295"}]}],"configurations":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:a:golang:go:*:*:*:*:*:*:*:*","versionEndExcluding":"1.24.13","matchCriteriaId":"9FEE539A-EDC2-4044-A38C-5A0FDF567509"},{"vulnerable":true,"criteria":"cpe:2.3:a:golang:go:*:*:*:*:*:*:*:*","versionStartIncluding":"1.25.0","versionEndExcluding":"1.25.7","matchCriteriaId":"B275853C-E253-485B-B469-31D1A7383965"},{"vulnerable":true,"criteria":"cpe:2.3:a:golang:go:1.26.0:rc1:*:*:*:*:*:*","matchCriteriaId":"E529A0EC-B944-4E2F-B26A-2A9F31AFF240"},{"vulnerable":true,"criteria":"cpe:2.3:a:golang:go:1.26.0:rc2:*:*:*:*:*:*","matchCriteriaId":"553D6D90-140E-4A54-86A3-00E66AC30F3C"}]}]}],"references":[{"url":"https://go.dev/cl/737700","source":"security@golang.org","tags":["Patch"]},{"url":"https://go.dev/issue/77217","source":"security@golang.org","tags":["Exploit","Issue Tracking"]},{"url":"https://groups.google.com/g/golang-announce/c/K09ubi9FQFk","source":"security@golang.org","tags":["Mailing List","Third Party Advisory"]},{"url":"https://pkg.go.dev/vuln/GO-2026-4337","source":"security@golang.org","tags":["Vendor Advisory"]}]}}]}