Repository compromise via privileged fork code execution
Published Apr 24, 2026 · Updated Apr 24, 2026
Code injection in the skim repository allows remote attackers to execute fork code in a privileged GitHub Actions workflow. The generate-files job uses pull_request_target, checks out the pull request head from an attacker-controlled fork, and passes it to cargo run while repository tokens are available. Opening a fork pull request triggers the job without a label or approval gate, enabling theft of the app token and writes to nonprotected branches and tags.
Summary
What happened
Code injection in the skim repository allows remote attackers to execute fork code in a privileged GitHub Actions workflow. The generate-files job uses pull_request_target, checks out the pull request head from an attacker-controlled fork, and passes it to cargo run while repository tokens are available. Opening a fork pull request triggers the job without a label or approval gate, enabling theft of the app token and writes to nonprotected branches and tags.
The record
- CVE
- CVE-2026-41414
- Published
- Apr 24, 2026
- Updated
- Apr 24, 2026
- Vendor
- skim-rs
- Product
- skim
- Classifications
- CWE-94, T1195.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 24, 2026CVE publishedPublication date reported by the CVE source.
- Apr 24, 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=< bf63404ad51985b00ed304690ba9d477860a5a75
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.
Weakness, pattern, technique
Public exploit references
- Replica pull_request_target token-exfiltration demonstrationproof 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