CVE-2026-41414 Skim Rs CVE debrief

Who should care

Defenders responsible for Skim installations and GitHub users who open pull requests from forks should assess exposure and prioritize remediation. This includes verifying the presence of vulnerable Skim installations, reviewing compensating controls, and monitoring GitHub pull requests for suspicious activity. Additionally, security teams should assess the impact of exploitation on sensitive environment variables and plan vendor-supported updates or mitig.

Why it matters

CVE-2026-41414 is a high-severity vulnerability in Skim that allows attackers to execute arbitrary code via a GitHub pull request, requiring defenders to verify exposure and remediate vulnerable installations.

• Verify exposure of Skim installations to arbitrary code execution
• Remediate vulnerable Skim installations to prevent exploitation
• Monitor GitHub pull requests for suspicious activity
• Assess impact of exploitation on sensitive environment variables

Technical summary

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). This allows attackers to execute arbitrary code, potentially leading to a compromise of sensitive environment variables. The vulnerability is fixed with commit bf63404ad51985b00ed304690ba9d477860a5a75, which likely addresses the insecure code execution mechanism. However, defenders must verify exposure and remediate vulnerable installations to prevent exploitation.

Defensive priority

Defenders should prioritize verifying exposure and remediating vulnerable Skim installations.

Recommended defensive actions

• Verify Skim installations for exposure
• Remediate vulnerable Skim installations
• Monitor GitHub pull requests for suspicious activity
• Review compensating controls for exposed systems
• Check relevant monitoring, detection, and logs for exposed assets
• Track exceptions and retest remediated assets
• Plan vendor-supported updates through normal change control

Evidence notes

The vulnerability is caused by the generate-files job in .github/workflows/pr.yml checking out attacker-controlled fork code and executing it via cargo run, with access to sensitive environment variables such as SKIM_RS_BOT_PRIVATE_KEY and GITHUB_TOKEN (contents:write). The lack of gates to prevent exploitation means that any GitHub user can trigger this vulnerability by opening a pull request from a fork. To verify exposure, defenders should review their Skim installations and assess the impact of exploitation on sensitive variables.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.