Command execution via ambiguous VCS metadata resolution
Published Jul 29, 2025 · Updated Nov 4, 2025
Command execution in Google Cloud Go command before 1.23.11 and 1.24.0 through 1.24.4 allows attackers to run commands via untrusted VCS repositories. The toolchain's VCS status resolver searches repository roots to embed build metadata and invokes the selected VCS without rejecting multiple or nested VCS metadata directories. A user must run the toolchain inside a repository fetched by another VCS; modules retrieved through go get are unaffected.
Summary
What happened
Command execution in Google Cloud Go command before 1.23.11 and 1.24.0 through 1.24.4 allows attackers to run commands via untrusted VCS repositories. The toolchain's VCS status resolver searches repository roots to embed build metadata and invokes the selected VCS without rejecting multiple or nested VCS metadata directories. A user must run the toolchain inside a repository fetched by another VCS; modules retrieved through go get are unaffected.
The record
- CVE
- CVE-2025-4674
- Published
- Jul 29, 2025
- Updated
- Nov 4, 2025
- Vendor
- Google Cloud
- Product
- Go command
- Classifications
- CWE-73, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 29, 2025CVE publishedPublication date reported by the CVE source.
- Nov 4, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.23.11
- Affected versionversion=1.24.0-0 <1.24.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo