Vulnerability in gix-sec (CVE-2025-24890)
Summary
Vulnerability in gix-sec (CVE-2025-24890). Confidential information can be exposed externally. Exploitable via safe.directory. Mitigation: upgrade to 0.13.3 or later.
Original description
The description as published by the source.
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 administrators should be able to use what are, conceptually, their own repositories. So Git considers administrators (when operating this way) to own them.
Code in gix-sec intends to implement a similar check. But after finding that it is run with an administrative token, it needs to check if the directory is owned by the Administrators group, yet instead accidentally examines itself again, rather than the directory.
Specifically…
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-24890 has been found in gix-sec.
Attackers can target a specific entry point like safe.directory over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.8/10.
What to do: upgrade gix-sec to 0.13.3 or later.
If unsure, ask your IT team or search "gix-sec CVE-2025-24890" on the vendor's site.
CVE-2025-24890 (gix-sec) — CWE-283 / CVSS v3 6.8
Attack vector: local
Attack surface: safe.directory / Administrators / is_path_owned_by_current_user / folder_owner
Patched: 0.13.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-283) exists in gix-sec. Attackers reach the vulnerable code path via safe.directory.
Check the vendor advisory for the affected versions of gix-sec. Attack surface: safe.directory / Administrators / is_path_owned_by_current_user / folder_owner.
Severity: Medium (CVSS 6.8/10). Confidential information can be exposed externally.
Update to 0.13.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'gix-sec' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'gix-sec' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
gix-secを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade gix-sec to 0.13.3ステージング環境で 0.13.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。