Administrator code execution via mistaken token-owner checks
Published Sep 14, 2026 · Updated Sep 14, 2026
Unverified ownership in gitoxide before 0.13.3 allows local users to execute commands as an elevated Windows administrator. The Windows is_path_owned_by_current_user check passes token_owner to administrator SID and membership checks instead of validating folder_owner. Exploitation requires a limited user-controlled repository, an unfiltered elevated administrator token, a dependent operation that trusts gix-sec, and interaction with configuration or hooks; cloning is unaffected.
Summary
What happened
Unverified ownership in gitoxide before 0.13.3 allows local users to execute commands as an elevated Windows administrator. The Windows is_path_owned_by_current_user check passes token_owner to administrator SID and membership checks instead of validating folder_owner. Exploitation requires a limited user-controlled repository, an unfiltered elevated administrator token, a dependent operation that trusts gix-sec, and interaction with configuration or hooks; cloning is unaffected.
The record
- CVE
- CVE-2025-24890
- Published
- Sep 14, 2026
- Updated
- Sep 14, 2026
- Vendor
- GitoxideLabs
- Product
- gitoxide
- Classifications
- CWE-283, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 14, 2026CVE publishedPublication date reported by the CVE source.
- Sep 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.13.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Upstream gix fetch proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo