CVE-2025-22873: Improper access to parent directory of root in os
Noroxi assessment
Priority: Monitor (action score 15/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Go standard library os 1.23.9, 1.24.3.
Low priority for now. Upgrade to Go standard library os 1.23.9, 1.24.3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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 ancestors of the parent or files contained within the parent.
- Published
- Feb 4, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 14th percentile
- CWE
- CWE-23
Report tools
Action score
15
Monitor
Low priority for now.
- CVSS
- 15 / 40 · 3.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| golang | go | cpe:2.3:a:golang:go |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- golang gobefore 1.23.9
- golang go1.24.0 and later · before 1.24.3
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Go). Independent of NVD's CPE analysis and usually ahead of it.
Go standard library os
- before 1.23.9affected · semver
- 1.24.0-0 and later · before 1.24.3affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | golang-1.24 | before 1.24.4-1 | 1.24.4-1 |
| Go | stdlib | from 1.24.0-0 · before 1.24.3 | 1.24.3 |
| Go | stdlib | before 1.23.9 | 1.23.9 |
| openSUSE:Leap 15.6 | go1.24 | before 1.24.4-150000.1.26.1 | 1.24.4-150000.1.26.1 |
| openSUSE:Leap 15.6 | go1.24 | before 1.24.3-150000.1.23.1 | 1.24.3-150000.1.23.1 |
| openSUSE:Leap 15.6 | govulncheck-vulndb | before 0.0.20260205T172317-150000.1.146.1 | 0.0.20260205T172317-150000.1.146.1 |
| openSUSE:Tumbleweed | go1.24 | before 1.24.3-1.1 | 1.24.3-1.1 |
| Red Hat:hummingbird:1 | golang1.25 | before 0:1.25.9-1.hum1 | 0:1.25.9-1.hum1 |
| Red Hat:hummingbird:1 | golang1.25-bin | before 0:1.25.9-1.hum1 | 0:1.25.9-1.hum1 |
| Red Hat:hummingbird:1 | golang1.25-docs | before 0:1.25.9-1.hum1 | 0:1.25.9-1.hum1 |
| Red Hat:hummingbird:1 | golang1.25-misc | before 0:1.25.9-1.hum1 | 0:1.25.9-1.hum1 |
| Red Hat:hummingbird:1 | golang1.25-shared | before 0:1.25.9-1.hum1 | 0:1.25.9-1.hum1 |
| Red Hat:hummingbird:1 | golang1.25-src | before 0:1.25.9-1.hum1 | 0:1.25.9-1.hum1 |
| Red Hat:hummingbird:1 | golang1.25-tests | before 0:1.25.9-1.hum1 | 0:1.25.9-1.hum1 |
| Red Hat:hummingbird:1 | golang1.26 | before 0:1.26.2-1.hum1 | 0:1.26.2-1.hum1 |
| Red Hat:hummingbird:1 | golang1.26-bin | before 0:1.26.2-1.hum1 | 0:1.26.2-1.hum1 |
| Red Hat:hummingbird:1 | golang1.26-docs | before 0:1.26.2-1.hum1 | 0:1.26.2-1.hum1 |
| Red Hat:hummingbird:1 | golang1.26-misc | before 0:1.26.2-1.hum1 | 0:1.26.2-1.hum1 |
| Red Hat:hummingbird:1 | golang1.26-shared | before 0:1.26.2-1.hum1 | 0:1.26.2-1.hum1 |
| Red Hat:hummingbird:1 | golang1.26-src | before 0:1.26.2-1.hum1 | 0:1.26.2-1.hum1 |
| Red Hat:hummingbird:1 | golang1.26-tests | before 0:1.26.2-1.hum1 | 0:1.26.2-1.hum1 |
| SUSE:Linux Enterprise Module for Development Tools 15 SP6 | go1.24 | before 1.24.4-150000.1.26.1 | 1.24.4-150000.1.26.1 |
| SUSE:Linux Enterprise Module for Development Tools 15 SP7 | go1.24 | before 1.24.3-150000.1.23.1 | 1.24.3-150000.1.23.1 |
Same product
golang: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-7187The "go get" implementation in Go 1.9.4, when the -insecure command-line option is used, does not validate the import path (get/vcs.go only 54Plan
- CVE-2018-16873In Go before 1.10.6 and 1.11.x before 1.11.3, the "go get" command is vulnerable to remote code execution when executed with the -u flag and52Plan
- CVE-2021-38297Go before 1.16.9 and 1.17.x before 1.17.2 has a Buffer Overflow via large arguments in a function invocation from a WASM module, when GOARCH42Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-61731Jan 28, 2026 · Arbitrary file write using cgo pkg-config directive in cmd/go31Monitor
- ← EarlierCVE-2025-68119Jan 28, 2026 · Unexpected code execution when invoking toolchain in cmd/go28Monitor
- Later →CVE-2025-61732Feb 5, 2026 · Potential code smuggling via doc comments in cmd/cgo34Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Go standard library os | 1.23.9 | Vendor (CNA) |
| Go standard library os | 1.24.3 | Vendor (CNA) |
| debian:golang-1.24 | 1.24.4-1 · Debian:13 | Package registry (OSV) |
| Go:stdlib | 1.23.9 | Package registry (OSV) |
| Go:stdlib | 1.24.3 | Package registry (OSV) |
| opensuse:go1.24 | 1.24.4-150000.1.26.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:govulncheck-vulndb | 0.0.20260205T172317-150000.1.146.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| red hat:golang1.25 | 0:1.25.9-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:golang1.25-bin | 0:1.25.9-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:golang1.25-docs | 0:1.25.9-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:golang1.25-misc | 0:1.25.9-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:golang1.25-shared | 0:1.25.9-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:golang1.26 | 0:1.26.2-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:golang1.26-bin | 0:1.26.2-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:golang1.26-docs | 0:1.26.2-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:golang1.26-misc | 0:1.26.2-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:golang1.26-shared | 0:1.26.2-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:golang1.26-src | 0:1.26.2-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:golang1.26-tests | 0:1.26.2-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| suse:go1.24 | 1.24.3-150000.1.23.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP7 | Package registry (OSV) |
| suse:go1.24 | 1.24.4-150000.1.26.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP6 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Dan Sebastian ThraneSDU eScience Center
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
—
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
- CVE-2026-3381062 days apartCase-sensitive excludedSubtrees name constraints cause Auth Bypass in crypto/x50932Monitor
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-23 · Relative Path TraversalCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.