gix-worktree-state nonexclusive checkout sets executable files world-writable

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.0 · CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:N

EPSS

• CVE-2025-22620: 0.37% estimated exploitation activity in the next 30 days; percentile 31.20 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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. Details Git repositories track executable bits for regular files. In tree objects and the index, regular file modes are stored as 0644 if not executable, or 0755 if executable. But this is independent of how the permissions are set in the filesystem (where supported). gixworktreestate::checkout has two strategies for checking out a file and marking it executable on a Unix-like operating system, one of which is vulnerable: - If the file is created by assuming it does not already exist, correct permissions are applied, because permissions specified when opening a file are subject to the umask. - If the file is considered possibly already to exist—even in a clean checkout if the…

Published by the source

21 Jan 2025, 21:13 UTC

Last modified by the source

21 Jan 2025, 21:13 UTC

Source last checked

26 Oct 2026, 15:38 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-fqmf-w4xh-33rh

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-22620

Advisory: gix-worktree-state nonexclusive checkout sets executable files world-writable
IDs: CVE-2025-22620, GHSA-fqmf-w4xh-33rh
Record: https://patchnext.com/advisories/cve-2025-22620 (revision 1, source checked 26 Oct 2026, 15:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: gix-worktree-state 0.17.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io gix-worktree-state: affected < 0.17.0; fixed in 0.17.0

## Suggested inspection (read-only)
- crates.io gix-worktree-state: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on gix-worktree-state.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-fqmf-w4xh-33rh (GitHub-reviewed advisory GHSA-fqmf-w4xh-33rh lists affected ranges: crates.io gix-worktree-state >=0 <0.17.0)

Commands are suggestions: review each one before running it.