CVE-2025-47910VulnerabilityPublished 12 Dec 2025Updated 1 Nov 2026

SUSE · Security update for go1.25

Affects SUSESource GCVE Database

Compare

Authoritative record:CVE-2025-47910· Medium 5.4

Not known to be exploited · CVSS 5.4 Medium.

Data as of 1 Nov 2026, 12:27 UTC

CVSS 3.1 base score

5.4Medium

How severe the flaw is on the 0–10 CVSS scale.

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

A fixed version is available: Go 1.25.5. Users should update to this version to remediate the listed vulnerabilities. No additional mitigation steps are indicated beyond applying this security update.

Description

This security update for Go version 1.25 addresses multiple vulnerabilities including excessive resource consumption, memory exhaustion, parsing errors, and information leakage across various Go standard library packages. The update advances to version 1.25.5 and fixes issues such as excessive CPU usage in net/mail and net/textproto, quadratic complexity in encoding/pem and crypto/x509, and insecure bypass patterns in net/http CrossOriginProtection. Additional fixes include panic conditions and validation errors in crypto/x509 and crypto/tls. The update also resolves other non-security bugs and improves compatibility and stability.

Impact

The vulnerabilities fixed in this update can lead to excessive CPU and memory consumption, potentially causing denial of service conditions. Some flaws allow attacker-controlled information to be leaked in error messages, and others cause panics or crashes during certificate validation or parsing operations. The net/http CrossOriginProtection flaw could allow insecure bypass patterns, weakening security controls. Overall, these issues could degrade application availability and security if exploited.

Summary

The Go 1.25 security update (to version 1.25.5) fixes numerous security vulnerabilities affecting core packages such as crypto/x509, net/mail, net/textproto, encoding/pem, crypto/tls, net/http, encoding/asn1, archive/tar, and net/url. Notable vulnerabilities include excessive resource consumption leading to potential denial of service, memory exhaustion due to unbounded allocations, information disclosure via ALPN negotiation errors, and validation flaws in certificate handling and HTTP protections. The update also addresses various panics and parsing regressions. These fixes collectively improve the security posture of Go 1.25 by mitigating risks of resource exhaustion, denial of service, and information leakage.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 1 Nov 2026, 12:27 UTC

Technical details

References

Community reviews

Related threats