Cyber Resilience

CVE-2025-22873

Path Traversal in Golang Go ≤ 1.23.9

Path Traversal
Published
04 February 2026
Modified
10 February 2026
Patch / advisory
View advisory
CVSS Score v3.1 3.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N
EPSS Score 0.0024 15th percentile
Risk Priority 30 floored blend · peak EPSS

Summary

CVE-2025-22873 is a low-severity Relative Path Traversal (CWE-23) vulnerability in Golang Go. Its CVSS base score is 3.8 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 15th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A01:2025 Broken Access Control

EU & UK References

Vulnerability Data

It was possible to improperly access the parent directory of an os.Root by opening a filename ending in "../". For example, Root.Open("../") would open the parent directory of the Root. This escape only permits opening the parent directory itself, not…

more

ancestors of the parent or files contained within the parent.

CWE(s)
CWE-23

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-27139Same product: Golang Go
CVE-2025-4674Same product: Golang Go
CVE-2023-29406Same product: Golang Go
CVE-2026-25679Same product: Golang Go
CVE-2023-24537Same product: Golang Go
CVE-2025-58189Same product: Golang Go
CVE-2026-27140Same product: Golang Go
CVE-2026-39826Same product: Golang Go
CVE-2026-32289Same product: Golang Go
CVE-2026-39823Same product: Golang Go

Affected Assets

golang
go
≤ 1.23.9 · 1.24.0 — 1.24.3

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V5.3.2

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match

Explicit validation of path inputs stops .. sequences from ever being interpreted by the file system.

AC-3 Access Enforcement partial match

Access enforcement directly blocks unauthorized file reads/writes that result from unresolved .. sequences.

AC-4 Information Flow Enforcement partial match

Information-flow rules can be configured to reject traversals that would move data outside an approved directory boundary.

AC-6 Least Privilege partial match

Least privilege reduces the set of reachable files even when a traversal succeeds.

SA-8 Security and Privacy Engineering Principles partial match

Secure-engineering principles require safe pathname construction and input neutralization before any file operation.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and path sanitization that prevent relative traversal.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development catches path traversal via static/dynamic analysis, but does not itself implement the fix.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and path-handling controls that directly prevent relative path traversal.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for controls against path traversal and other injection flaws.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles include directory isolation and canonicalization, reducing but not eliminating traversal risk.

A.8.28 Secure coding partial match
prevents

Secure coding standards require neutralizing path traversal sequences, directly addressing CWE-23.

A.8.3 Information access restriction partial match
mitigates

Information access restriction limits which files can be reached, mitigating impact but not preventing the traversal flaw.

References