CVE-2025-22620

CVE-2025-22620 is a medium-severity vulnerability with a CVSS 3.x base score of 5.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-281.

Key facts

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.

Frequently asked questions

What is CVE-2025-22620?
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.
How severe is CVE-2025-22620?
CVE-2025-22620 has a CVSS 3.x base score of 5.0, rated medium severity. It is exploitable over local access with low attack complexity, requires low privileges and user interaction. Impact on confidentiality is none, integrity high, and availability none.
Is CVE-2025-22620 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (28th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2025-22620?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-22620 have an EU (EUVD) identifier?
Yes. CVE-2025-22620 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-0160.
When was CVE-2025-22620 published?
CVE-2025-22620 was published on 2025-01-20 and last updated on 2026-06-17.

References

Other CWE-281 (Improper Preservation of Permissions) vulnerabilities

Browse all CWE-281 (Improper Preservation of Permissions) vulnerabilities →