Menu

Star on GitHub · 3.2k

CVE-2025-22620

5.0 · MEDIUM

gitoxide is an implementation of git written in Rust.

Published Jan 20, 2025CWE-281EPSS 0.37%

Overview

CVE-2025-22620 is a medium-severity vulnerability. It was published on January 20, 2025 and has a CVSS 3.1 base score of 5.0 (MEDIUM).

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

Technical description

gitoxide is an implementation of git written in Rust. Prior to 0.17.0, gix-worktree-state specifies 0777 permissions when checking out executable files, intending that the umask will restrict them appropriately. But one of the strategies it uses to set permissions is not subject to the umask. This causes files in a repository to be world-writable in some situations. This vulnerability is fixed in 0.17.0.

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-22620?

CVE-2025-22620 is a medium-severity vulnerability. It was published on January 20, 2025 and has a CVSS 3.1 base score of 5.0 (MEDIUM).

How severe is CVE-2025-22620?

This vulnerability has a CVSS 3.1 base score of 5.0, rated MEDIUM. 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-22620?

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-22620?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-22620 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 MEDIUM CVEs from 2025

View all