CVE-2025-61727

Published Dec 3, 2025

Last updated 6 months ago

Overview

AI description

Automated description summarized from trusted sources.

CVE-2025-61727 refers to a security vulnerability found in Go versions 1.25.5 and 1.24.11. Specifically, an excluded subdomain constraint in a certificate chain does not restrict the usage of wildcard SANs in the leaf certificate. For example, a constraint that excludes the subdomain test.example.com does not prevent a leaf certificate from claiming the SAN *.example.com. This vulnerability could allow a malicious actor to bypass intended security restrictions related to certificate validation. The issue is addressed in Go versions 1.25.5 and 1.24.11.

Description
An excluded subdomain constraint in a certificate chain does not restrict the usage of wildcard SANs in the leaf certificate. For example a constraint that excludes the subdomain test.example.com does not prevent a leaf certificate from claiming the SAN *.example.com.
Source
security@golang.org
NVD status
Analyzed
Products
go

Risk scores

CVSS 3.1

Type
Secondary
Base score
6.5
Impact score
2.5
Exploitability score
3.9
Vector string
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Severity
MEDIUM

Weaknesses

nvd@nist.gov
CWE-295

Social media

Hype score
Not currently trending
  1. Critical Go sec update for #Mageia 9: MGASA-2025-0326 patches CVE-2025-61727 (DNS constraint bypass in crypto/x509) & CVE-2025-61729 (resource exhaustion DoS). Read more: ๐Ÿ‘‰ https://t.co/84x7Bln9EY #Security https://t.co/RYWVRzshYk

    @Cezar_H_Linux

    13 Dec 2025

    34 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  2. openSUSE releases Go 1.24.11 and 1.25.5 updates fixing crypto/x509 flaws CVE-2025-61727 and CVE-2025-61729 that can cause resource exhaustion and cert validation issues. #Vulnerability https://t.co/M1qJQmfpsR

    @threatcluster

    10 Dec 2025

    24 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  3. ๐Ÿ” Critical update for @openSUSE #Tumbleweed users: Advisory 2025:15796-1 patches two "important" severity vulnerabilities in go1.24 (CVE-2025-61727/61729). One allows resource exhaustion via malicious certs. Read more: ๐Ÿ‘‰ https://t.co/12pjW0j7Vv #Security https://t.co/7E9

    @Cezar_H_Linux

    5 Dec 2025

    5 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  4. CVE-2025-61727 An excluded subdomain constraint in a certificate chain does not restrict the usage of wildcard SANs in the leaf certificate. For example a constraint that excludes tโ€ฆ https://t.co/JwusLOYNU5

    @CVEnew

    3 Dec 2025

    163 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  5. ๐ŸŽ‰ Go 1.25.5 and 1.24.11 are released! ๐Ÿ” Security: Includes security fixes for crypto/x509 (CVE-2025-61729, CVE-2025-61727). ๐Ÿ—ฃ Announcement: https://t.co/zG9tCI47Nf โฌ‡๏ธ Download: https://t.co/d45S6FsIsY #golang https://t.co/w6hYSx5Upg

    @golang

    2 Dec 2025

    27211 Impressions

    102 Retweets

    662 Likes

    26 Bookmarks

    12 Replies

    10 Quotes

Configurations

  1. A malicious module proxy can exploit a flaw in the go command's validation of module checksums to bypass checksum database validation. This vulnerability affects any user using an untrusted module proxy (GOMODPROXY) or checksum database (GOSUMDB). A malicious module proxy can serve altered versions of the Go toolchain. When selecting a different version of the Go toolchain than the currently installed toolchain (due to the GOTOOLCHAIN environment variable, or a go.work or go.mod with a toolchain line), the go command will download and execute a toolchain provided by the module proxy. A malicious module proxy can bypass checksum database validation for this downloaded toolchain. Since this vulnerability affects the security of toolchain downloads, setting GOTOOLCHAIN to a fixed version is not sufficient. You must upgrade your base Go toolchain. The go tool always validates the hash of a toolchain before executing it, so fixed versions will refuse to execute any cached, altered versions of the toolchain. The go tool trusts go.sum files to contain accurate hashes of the current module's dependencies. A malicious proxy exploiting this vulnerability to serve an altered module will have caused an incorrect hash to be recorded in the go.sum. Users who have configured a non-trusted GOPROXY can determine if they have been affected by running "rm go.sum ; go mod tidy ; go mod verify", which will revalidate all dependencies of the current module. The specific flaw in more detail: The go command consults the checksum database to validate downloaded modules, when a module is not listed in the go.sum file. It verifies that the module hash reported by the checksum database matches the hash of the downloaded module. If, however, the checksum database returns a successful response that contains no entry for the module, the go command incorrectly permitted validation to succeed. A module proxy may mirror or proxy the checksum database, in which case the go command will not connect to the checksum database directly. Checksums reported by the checksum database are cryptographically signed, so a malicious proxy cannot alter the reported checksum for a module. However, a proxy which returns an empty checksum response, or a checksum response for an unrelated module, could cause the go command to proceed as if a downloaded module has been validated.โ€ขCVE-2026-42501