Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:NSummary
CVE-2026-41414 is a high-severity Code Injection (CWE-94) vulnerability in Skim-Rs Skim. Its CVSS base score is 7.4 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked at the 20th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-41414 is a code injection vulnerability (CWE-94) in the GitHub Actions workflow of Skim, a Rust-based fuzzy finder tool for navigating files, lines, and commands, hosted in the skim-rs/skim repository. The issue resides in the generate-files job defined in .github/workflows/pr.yml, which checks out code from attacker-controlled forks and executes it using cargo run. This workflow has access to sensitive secrets, including SKIM_RS_BOT_PRIVATE_KEY and GITHUB_TOKEN with contents:write permissions. The vulnerability carries a CVSS v3.1 base score of 7.4 (AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N) and was published on 2026-04-24.
Any GitHub user can exploit this vulnerability by forking the repository and opening a pull request, as there are no protective gates to prevent execution of the forked code. Upon triggering the workflow, the attacker achieves arbitrary code execution in the context of the repository's CI environment, granting access to the exposed secrets. This enables actions such as writing to the repository contents via the GITHUB_TOKEN and potential misuse of the SKIM_RS_BOT_PRIVATE_KEY, resulting in high integrity impact with a changed scope.
The vulnerability has been fixed in commit bf63404ad51985b00ed304690ba9d477860a5a75, as detailed in the project's GitHub security advisory (GHSA-9g93-rxr5-xhqw). Security practitioners should ensure repositories update to this commit or later, review workflows for similar PR-triggered secret exposures, and enable branch protection rules or workflow permissions to restrict untrusted code execution.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-25596
Vulnerability Data
Skim is a fuzzy finder designed to through files, lines, and commands. The generate-files job in .github/workflows/pr.yml checks out attacker-controlled fork code and executes it via cargo run, with access to SKIM_RS_BOT_PRIVATE_KEY and GITHUB_TOKEN (contents:write). No gates prevent exploitation -…
more
any GitHub user can trigger this by opening a pull request from a fork. This vulnerability is fixed with commit bf63404ad51985b00ed304690ba9d477860a5a75.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.3.1
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation finds code paths that accept and execute externally influenced strings.
Input validation directly stops untrusted data from being used to construct executable code without neutralization.
Least privilege limits the damage an injected code fragment can perform once executed.
Requiring documented secure development standards and tools enforces use of safe code-generation APIs and escaping.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
PR.PS-06's SDLC practices directly target injection flaws via secure coding and testing (mostly), yet as a single broad outcome it leaves many code-generation specifics unaddressed (partial).
PR.DS-10 protects runtime data confidentiality/integrity but has no bearing on neutralizing externally influenced input during code generation, so neither direction shows any preventive effect.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Banning unapproved code samples and unauthenticated web services, combined with secure-coding standards and SAST, prevents the dynamic generation or inclusion of attacker-supplied code.
Controls that restrict unauthorized or malicious code from being introduced via external networks or removable media limit opportunities for an attacker to inject and execute arbitrary code.