cve.bz

CVE-2025-0913 golang go: Link Following

5.5 mediumEPSS 0.3%Fix available

Medium (5.5) in golang go. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in stdlib 1.23.10, 1.24.4.

On this page
os.OpenFile(path, os.O_CREATE|O_EXCL) behaved differently on Unix and Windows systems when the target path was a dangling symlink. On Unix systems, OpenFile with O_CREATE and O_EXCL flags never follows symlinks. On Windows, when the target path was a symlink to a nonexistent location, OpenFile would create a file in that location. OpenFile now always returns an error when the O_CREATE and O_EXCL flags are both set and the target path is a symlink.

Severity

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 26th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-06-11. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-59 Improper Link Resolution Before File Access (Link Following)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-0913 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-0913?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-0913?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-0913 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Go standard library syscallbefore 1.23.10
Go standard library syscallfrom 1.24.0-0 before 1.24.4
Go standard library osbefore 1.23.10
Go standard library osfrom 1.24.0-0 before 1.24.4

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GO-2025-3750Gostdlib<1.23.10
>=1.24.0-0 <1.24.4
1.23.10, 1.24.4

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu14.04:LTSgolang-1.10no fix listedUBUNTU-CVE-2025-0913
Ubuntu16.04:LTSgolang-1.6, golang-1.10no fix listedUBUNTU-CVE-2025-0913
Ubuntu18.04:LTSgolang-1.8, golang-1.9, golang-1.10no fix listedUBUNTU-CVE-2025-0913
Ubuntu20.04:LTSgolang-1.13, golang-1.14, golang-1.18 and 3 moreno fix listedUBUNTU-CVE-2025-0913
Ubuntu22.04:LTSgolang-1.13, golang-1.17, golang-1.18 and 5 moreno fix listedUBUNTU-CVE-2025-0913
Ubuntu24.04:LTSgolang-1.21, golang-1.22, golang-1.23no fix listedUBUNTU-CVE-2025-0913
Ubuntu25.10, 26.04:LTSgolang-1.23, golang-1.24no fix listedUBUNTU-CVE-2025-0913
UbuntuPro:16.04:LTSgolang-1.13, golang-1.18no fix listedUBUNTU-CVE-2025-0913
UbuntuPro:18.04:LTSgolang-1.13, golang-1.16, golang-1.18no fix listedUBUNTU-CVE-2025-0913
UbuntuPro:20.04:LTSgolang-1.16no fix listedUBUNTU-CVE-2025-0913
SUSEEnterprise Storage 7.1, Linux Enterprise High Performance Computing 15 SP3-LTSS, Linux Enterprise High Performance Computing 15 SP4-ESPOS and 11 morego1.231.23.10-150000.1.34.1SUSE-SU-2025:01848-1
SUSEEnterprise Storage 7.1, Linux Enterprise High Performance Computing 15 SP3-LTSS, Linux Enterprise High Performance Computing 15 SP4-ESPOS and 11 morego1.241.24.4-150000.1.26.1SUSE-SU-2025:01846-1
SUSEEnterprise Storage 7.1, Linux Enterprise High Performance Computing 15 SP3-LTSS, Linux Enterprise High Performance Computing 15 SP4-ESPOS and 9 morego1.24-openssl1.24.4-150000.1.9.1SUSE-SU-2025:02120-1
SUSELinux Enterprise Module for Development Tools 15 SP6, Linux Enterprise Module for Development Tools 15 SP7go1.23-openssl1.23.12-150600.13.9.1SUSE-SU-2025:03159-1
SUSELinux Enterprise Module for Development Tools 15 SP6, Linux Enterprise Module for Development Tools 15 SP7go1.24-openssl1.24.6-150600.13.9.1SUSE-SU-2025:03158-1
openSUSELeap 15.6go1.231.23.10-150000.1.34.1SUSE-SU-2025:01848-1
openSUSELeap 15.6go1.23-openssl1.23.12-150600.13.9.1SUSE-SU-2025:03159-1
openSUSELeap 15.6go1.241.24.4-150000.1.26.1SUSE-SU-2025:01846-1
openSUSELeap 15.6go1.24-openssl1.24.6-150600.13.9.1SUSE-SU-2025:03158-1
openSUSETumbleweedgo1.231.23.10-1.1openSUSE-SU-2025:15223-1
openSUSETumbleweedgo1.241.24.4-1.1openSUSE-SU-2025:15224-1
openSUSETumbleweedgovulncheck-vulndb0.0.20250612T141001-1.1openSUSE-SU-2025:15225-1
openSUSETumbleweedkubecolor0.5.2-1.1openSUSE-SU-2025:15586-1
Alpinev3.22, v3.23, v3.24go1.24.4-r0ALPINE-CVE-2025-0913
Azure Linux3golangno fix listedAZL-78978 AZL-98823
Alpaquita23go1.23.10-r0BELL-CVE-2025-0913
Alpaquita25, streamgo1.24.4-r0BELL-CVE-2025-0913
BellSoft Hardened Containers23go1.23.10-r0BELL-CVE-2025-0913
BellSoft Hardened Containers25, streamgo1.24.4-r0BELL-CVE-2025-0913

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu · SUSE · openSUSE · Alpine · Alpaquita · BellSoft Hardened Containers.

Attack patterns (CAPEC)

  • CAPEC-17 Using Malicious Files Likelihood: High · Severity: Very High
  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-132 Symlink Attack Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON