Repository compromise via privileged untrusted checkout
Published Jan 27, 2026 · Updated Jan 27, 2026
QGIS repository automation allows remote authenticated users to execute code and compromise the repository through pull requests. The pre-commit checks workflow used pull_request_target, checked out an external pull request's head, and ran its pre-commit configuration with a write-scoped token. Opening a crafted pull request was sufficient to execute commands on the runner, read available secrets, and push repository changes.
Summary
What happened
QGIS repository automation allows remote authenticated users to execute code and compromise the repository through pull requests. The pre-commit checks workflow used pull_request_target, checked out an external pull request's head, and ran its pre-commit configuration with a write-scoped token. Opening a crafted pull request was sufficient to execute commands on the runner, read available secrets, and push repository changes.
The record
- CVE
- CVE-2026-24480
- Published
- Jan 27, 2026
- Updated
- Jan 27, 2026
- Vendor
- QGIS
- Product
- QGIS
- Classifications
- CWE-863, T1195.002
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 27, 2026CVE publishedPublication date reported by the CVE source.
- Jan 27, 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=< 76a693cd91650f9b4e83edac525e5e4f90d954e9
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
- Privileged pre-commit workflow 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