gix-sec safe.directory protections absent for elevated administrators

Exploitation

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

CVSS

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

EPSS

• CVE-2025-24890: 0.17% estimated exploitation activity in the next 30 days; percentile 5.71 (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 In a process run with full administrative rights on Windows, gix-sec wrongly treats all locations as trusted, leading to the execution of commands configured in repositories controlled by limited user accounts. Details In a similar way to Git, gitoxide tries to avoid operating in local repositories that it neither considers to be owned by the current user nor finds to match any value of safe.directory. This is because of the numerous commands that can be configured for a Git repository, to run as part of various actions, some of which even occur automatically due to the way custom shell prompts and text editors update their knowledge of repositories. On Unix-like operating systems, every directory is considered to be owned by some user ID. On Windows, other identities can own a directory in the same sense that a user can, and directories created while operating with full administrative rights default to being owned by the Administrators group, not the specific user. Such…

Published by the source

9 Sep 2026, 16:34 UTC

Last modified by the source

9 Sep 2026, 17:06 UTC

Source last checked

26 Oct 2026, 15:43 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-7rhf-42qf-vrvc

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-7rhf-42qf-vrvc

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

# Patch Next advisory brief: CVE-2025-24890

Advisory: gix-sec safe.directory protections absent for elevated administrators
IDs: CVE-2025-24890, GHSA-7rhf-42qf-vrvc
Record: https://patchnext.com/advisories/cve-2025-24890 (revision 2, source checked 26 Oct 2026, 15:43 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: gix-sec 0.13.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io gix-sec: affected <= 0.13.2; fixed in 0.13.3

## Suggested inspection (read-only)
- crates.io gix-sec: 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-sec.
- 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://osv.dev/vulnerability/GHSA-7rhf-42qf-vrvc (OSV record GHSA-7rhf-42qf-vrvc lists affected ranges: crates.io gix-sec >=0 <0.13.3 (fixed))
- Verified: https://github.com/advisories/GHSA-7rhf-42qf-vrvc (GitHub-reviewed advisory GHSA-7rhf-42qf-vrvc lists affected ranges: crates.io gix-sec >=0 <=0.13.2)

Commands are suggestions: review each one before running it.