CyberSecBulletin
CVE-2025-4674NVD status: Analyzed

cmd/go: External Control of File Name or Path

Published Updated By the CyberSecBulletin desk

CVE-2025-4674 is a high-severity external control of file name or path vulnerability in cmd/go from Go toolchain, with a CVSS 3.1 base score of 8.6 out of 10. It can be exploited with local access to the system by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. The record lists versions 1.23.11, 1.24.5 as the first without the flaw, so updating cmd/go to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.47% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update cmd/go to 1.23.11 or 1.24.5, whichever matches your release line, or a later version.
  2. Update Go to 1.23.11 or 1.24.5, whichever matches your release line, or a later version.
  3. Read the advisory on pkg.go.dev for workarounds and exact fixed builds.
  4. Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.

Affected products and versions

VendorProductAffected versionsFixed in
Go toolchaincmd/gobefore 1.23.11; 1.24.0-0 up to, but not including, 1.24.51.23.11, 1.24.5
GoGobefore 1.23.11; 1.24.0 up to, but not including, 1.24.51.23.11, 1.24.5

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
RequiredA user must take an action such as opening a file or link.
Scope
ChangedThe attack can reach beyond the vulnerable component into other systems.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H. Scored by CISA (ADP).

Official description

The go command may execute unexpected commands when operating in untrusted VCS repositories. This occurs when possibly dangerous VCS configuration is present in repositories. This can happen when a repository was fetched via one VCS (e.g. Git), but contains metadata for another VCS (e.g. Mercurial). Modules which are retrieved using the go command line, i.e. via "go get", are not affected.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: External Control of File Name or Path

The product allows user input to control or influence paths or file names that are used in filesystem operations.

How developers prevent this class of flaw

  • When the set of filenames is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames, and reject all other inputs. For example, ID 1 could map to inbox.txt and ID 2 could map to profile.txt. Features such as the ESAPI AccessReferenceMap provide this capability.
  • Run your code in a jail or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict all access to files within a particular directory. Examples include the Unix chroot jail and AppArmor. In general, managed code may provide some protection. This may not be a feasible solution, and it only limits the impact to the operating system; the rest of your application may still be subject to compromise. Be careful to avoid CWE-243 and other weaknesses related to jails.
  • For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.

More External Control of File Name or Path vulnerabilities (CWE-73)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Patches and release notes

Third-party and government advisories

Other vulnerabilities in cmd/go

All cmd/go vulnerabilities

Recent External Control of File Name or Path vulnerabilities

Spotted an error? Tell us.