Menu

Star on GitHub · 3.2k

CVE-2025-22873

3.8 · LOW

It was possible to improperly access the parent directory of an os.Root by opening a filename ending in "../".

Published Feb 4, 2026CWE-23EPSS 0.24%

Overview

CVE-2025-22873 is a low-severity vulnerability. It was published on February 4, 2026 and has a CVSS 3.1 base score of 3.8 (LOW).

This vulnerability has a CVSS 3.1 base score of 3.8, rated LOW. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2025-22873?

CVE-2025-22873 is a low-severity vulnerability. It was published on February 4, 2026 and has a CVSS 3.1 base score of 3.8 (LOW).

How severe is CVE-2025-22873?

This vulnerability has a CVSS 3.1 base score of 3.8, rated LOW. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2025-22873?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2025-22873?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-22873 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related LOW CVEs from 2025

View all