CVE-2025-0913: Go standard library syscall · Link Following
Affects Go standard library syscallSource CVE Database V5
Not known to be exploited · CVSS 5.5 Critical : upgrade to 1.24.4 or 1.23.10 as a priority.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.24.4, 1.23.10
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 11 Jun 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.
What to do
Upgrade syscall and os to 1.24.4 or 1.23.10.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Go standard librarysyscall | Affected
| Fixed in
|
| Go standard libraryos | Affected
| Fixed in
|
Gosyscallpkg:golang/syscallOther threats | Affected
| Fixed in
|
Goospkg:golang/osOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should avoid relying on os.OpenFile with O_CREATE and O_EXCL flags on Windows for paths that may be symlinks until an official fix is confirmed.
Description
CVE-2025-0913 is a vulnerability in the Go standard library syscall package related to improper link resolution before file access. The os.OpenFile function behaved inconsistently between Unix and Windows when handling dangling symbolic links with the O_CREATE and O_EXCL flags. On Unix, it did not follow symlinks, but on Windows, it created a file at the symlink's nonexistent target location. The issue is now fixed so that OpenFile returns an error when both flags are set and the target path is a symlink.