CVE-2025-4674VulnerabilityPublished 18 Aug 2025Updated 10 Sep 2026

Red Hat Security Advisory: golang security update

Affects Red HatSource GCVE Database

Authoritative record:CVE-2025-4674· High 8.6

Not known to be exploited · CVSS 8.6 High · patch available : patch Red Hat soon.

Data as of 26 Oct 2026, 07:57 UTC

CVSS base score

8.6High

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 2026-10-26.

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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC 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

Affected software

Product	Affected	Fixed in
Gogithub.com/golang/go/cmd/go`pkg:golang/github.com/golang/go/cmd/go`Other threats	Affected =0 =1.24.0-0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and has been released by Red Hat in golang version 1.24.6 for Red Hat Enterprise Linux 10. Users should update to this version or later to remediate the vulnerability. Refer to the Red Hat advisory RHSA-2025:13941 and the update article https://access.redhat.com/articles/11258 for detailed instructions on applying the update. No additional mitigations are indicated by the vendor advisory.

Description

The golang packages provide the Go programming language compiler. Security Fix(es): * cmd/go: Go VCS Command Execution Vulnerability (CVE-2025-4674) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Impact

The vulnerability allows potential command execution through the Go VCS command, which could lead to unauthorized actions on affected systems running vulnerable versions of the golang compiler. This could impact the security of software development and build processes that rely on the Go toolchain. No known exploits in the wild have been reported at this time.

Summary

The golang packages in Red Hat Enterprise Linux 10 contain a security vulnerability identified as CVE-2025-4674, which involves a command execution flaw in the cmd/go VCS command. This vulnerability is part of a set of three CVEs addressed in the advisory RHSA-2025:13941. The flaw could allow unintended command execution via the Go version control system command. Red Hat has issued patches in golang version 1.24.6 to fix this issue. The advisory covers multiple architectures including x86_64, s390x, ppc64le, and aarch64. No CVSS score is provided, but the severity is rated as high by Red Hat Product Security.

CWE-74Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Requirements
Programming languages and supporting technologies might be chosen which are not subject to these issues.
Implementation
Utilize an appropriate mix of allowlist and denylist parsing to filter control-plane syntax from all input.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
Injection Prevention (opens in a new tab)
SQL Injection Prevention (opens in a new tab)
Injection Prevention in Java (opens in a new tab)
OWASP ASVS 4.0.3
V1.5.1 (opens in a new tab)
Attack patterns
Buffer Overflow via Environment Variables (opens in a new tab)
Server Side Include (SSI) Injection (opens in a new tab)
HTTP Request Splitting (opens in a new tab)
Command Line Execution through SQL Injection (opens in a new tab)
Double Encoding (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-440Expected Behavior Violation (opens in a new tab)
Base weakness
A feature, API, or function does not perform according to its specification.
CWE-362Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') (opens in a new tab)
Class weaknessLikelihood of exploit: MediumOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
Architecture and Design
In languages that support it, use synchronization primitives. Only wrap these around critical code to minimize the impact on performance.
Architecture and Design
Use thread-safe capabilities such as the data access abstraction in Spring.
Architecture and Design
Minimize the usage of shared resources in order to remove as much complexity as possible from the control flow and to reduce the likelihood of unexpected conditions occurring.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V1.11.2 (opens in a new tab)
Attack patterns
Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions (opens in a new tab)
Leveraging Race Conditions (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Aug 2026, 19:58 UTC

WeaknessesCWE-74, CWE-440, CWE-362

Technical details

References

Community reviews

Related threats