CVE-2025-22873

LOWNVD 3.83.8—
EchelonGraph scoreMEDIUM confidence

Score 3.8 from GitHub Security Advisory (severity: LOW) published 2026-02-05. NVD baseline CVSS 3.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
3.8
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 3.8Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
3.8
EG Score
3.8(medium)
EPSS
14.7%
KEV
Not listed

Published

February 4, 2026

Last Modified

February 10, 2026

References (5)

Vendor Advisories for CVE-2025-22873(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatgolang1-25-main-1.25.9-1.hum12026-04-10redhat
redhatgolang1-26-main-1.26.2-1.hum12026-04-09redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
stdlib—1.24.3—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 50× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-16 17:02 UTCEPSS rescore
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 16:57 UTCEPSS rescore
  4. 2026-07-15 01:59 UTCEPSS rescore
  5. 2026-07-13 22:29 UTCEPSS rescore
  6. 2026-07-13 22:29 UTCEPSS rescore
  7. 2026-07-13 08:07 UTCOSV refresh
  8. 2026-07-13 06:12 UTCEPSS rescore
  9. 2026-07-13 06:12 UTCEPSS rescore
  10. 2026-07-12 05:46 UTCEPSS rescore
  11. 2026-07-12 05:46 UTCEPSS rescore
  12. 2026-07-11 08:27 UTCEPSS rescore
  13. 2026-07-11 08:26 UTCEPSS rescore
  14. 2026-07-09 19:09 UTCEPSS rescore
  15. 2026-07-08 15:14 UTCEPSS rescore
  16. 2026-07-07 13:45 UTCEPSS rescore
  17. 2026-07-06 16:26 UTCEPSS rescore
  18. 2026-07-06 02:22 UTCEPSS rescore
  19. 2026-07-06 02:22 UTCEPSS rescore
  20. 2026-07-05 02:30 UTCEPSS rescore
  21. 2026-07-01 15:06 UTCEPSS rescore
  22. 2026-06-30 23:21 UTCEPSS rescore
  23. 2026-06-30 23:21 UTCEPSS rescore
  24. 2026-06-29 14:06 UTCEPSS rescore
  25. 2026-06-28 14:07 UTCEPSS rescore
Show 53 more
  1. 2026-06-28 14:07 UTCEPSS rescore
  2. 2026-06-28 04:55 UTCEPSS rescore
  3. 2026-06-28 04:55 UTCEPSS rescore
  4. 2026-06-27 03:08 UTCEPSS rescore
  5. 2026-06-27 03:08 UTCEPSS rescore
  6. 2026-06-25 13:49 UTCEPSS rescore
  7. 2026-06-25 13:49 UTCEPSS rescore
  8. 2026-06-24 22:01 UTCOSV refresh
  9. 2026-06-24 14:04 UTCEPSS rescore
  10. 2026-06-24 14:04 UTCEPSS rescore
  11. 2026-06-23 21:32 UTCEPSS rescore
  12. 2026-06-23 21:32 UTCEPSS rescore
  13. 2026-06-22 14:25 UTCEPSS rescore
  14. 2026-06-22 14:25 UTCEPSS rescore
  15. 2026-06-21 14:56 UTCEPSS rescore
  16. 2026-06-21 14:56 UTCEPSS rescore
  17. 2026-06-21 01:59 UTCEPSS rescore
  18. 2026-06-21 01:59 UTCEPSS rescore
  19. 2026-06-19 19:25 UTCEPSS rescore
  20. 2026-06-19 19:25 UTCEPSS rescore
  21. 2026-06-18 17:52 UTCEPSS rescore
  22. 2026-06-18 17:52 UTCEPSS rescore
  23. 2026-06-17 17:52 UTCEPSS rescore
  24. 2026-06-16 17:52 UTCEPSS rescore
  25. 2026-06-16 17:52 UTCEPSS rescore
  26. 2026-06-15 17:48 UTCEPSS rescore
  27. 2026-06-14 23:17 UTCEPSS rescore
  28. 2026-06-13 22:59 UTCEPSS rescore
  29. 2026-06-11 13:59 UTCEPSS rescore
  30. 2026-06-10 13:22 UTCEPSS rescore
  31. 2026-06-08 14:16 UTCEPSS rescore
  32. 2026-06-08 14:16 UTCEPSS rescore
  33. 2026-06-07 21:26 UTCEG score recompute
  34. 2026-06-07 21:26 UTCVendor advisory
  35. 2026-06-07 21:26 UTCGHSA enrichment
  36. 2026-06-07 15:24 UTCEPSS rescore
  37. 2026-06-07 15:24 UTCEPSS rescore
  38. 2026-06-06 13:47 UTCEPSS rescore
  39. 2026-06-06 13:47 UTCEPSS rescore
  40. 2026-06-05 22:46 UTCEPSS rescore
  41. 2026-06-05 22:46 UTCEPSS rescore
  42. 2026-06-05 06:10 UTCEPSS rescore
  43. 2026-06-05 06:10 UTCEPSS rescore
  44. 2026-06-04 13:11 UTCEPSS rescore
  45. 2026-06-04 13:11 UTCEPSS rescore
  46. 2026-06-01 13:51 UTCEPSS rescore
  47. 2026-06-01 13:51 UTCEPSS rescore
  48. 2026-05-31 00:16 UTCEPSS rescore
  49. 2026-05-31 00:16 UTCEPSS rescore
  50. 2026-05-29 14:34 UTCEG score recompute
  51. 2026-05-29 14:34 UTCVendor advisory
  52. 2026-05-29 14:34 UTCGHSA enrichment
  53. 2026-05-29 13:44 UTCEPSS rescore

Frequently asked(5)

What is CVE-2025-22873?
CVE-2025-22873 is a low vulnerability published on February 4, 2026. 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…
When was CVE-2025-22873 disclosed?
CVE-2025-22873 was first published in the National Vulnerability Database on February 4, 2026, with the most recent update on February 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-22873 actively exploited?
CVE-2025-22873 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 14.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-22873?
CVE-2025-22873 has a CVSS v3 base score of 3.8 (NVD).
How do I remediate CVE-2025-22873?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-22873, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-22873

Explore →

Is Your Infrastructure Affected by CVE-2025-22873?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs