The vulnerability allows an attacker to execute arbitrary code within the CI environment of the Skim repository. The flaw resides in the generate-files job of the GitHub Actions workflow pr.yml, where code from an attacker‑controlled fork is uncheckedly checked out and run with cargo run, giving the process the SKIM_RS_BOT_PRIVATE_KEY and a GITHUB_TOKEN with contents:write permissions. This is a classic CWE‑94 scripting or code injection flaw. Successful exploitation would give the attacker full control over the CI run, enabling arbitrary command execution, secrets exfiltration, or deployment of malicious binaries.

Skim is an open‑source fuzzy finder maintained under skim-rs/skim. The affected component is the repository’s GitHub Actions workflow file pr.yml, which is part of every release of the project. No specific product release version number is listed in the advisory; the issue is fixed by the commit bf63404ad51985b00ed304690ba9d477860a5a75. Administrators using any version predating this commit are vulnerable.

The CVSS base score of 7.4 indicates a high‑severity vulnerability. The EPSS score is reported as < 1 %, implying that exploitation attempts are currently rare, and the vulnerability is not listed in the CISA KEV catalog. Nevertheless, the attack vector is server‑side code execution via GitHub Actions, which can be triggered by any public user submitting a pull request from a fork. Since the workflow runs with elevated tokens, the likelihood of an attacker successfully abusing it is high if an organization relies on the workflow unchanged. The lack of gates or checks means exploitation requires no additional privileges beyond authoring a fork.