Loading vulnerability…
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 - any GitHub user can trigger this by opening a pull request from a fork. This vulnerability is fixed with commit bf63404ad51985b00ed304690ba9d477860a5a75.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This 100-file Rust repository is a disposable research/lab snapshot of Skim 4.6.0, a terminal fuzzy finder (`sk`), rather than a conventional standalone exploit toolkit. Its primary application code is in `src/`, with the CLI entry point at `src/bin/main.rs`; fuzzy matching engines are in `src/engine/` and `src/fuzzy_matcher/`; examples, benchmarks, shell integrations, Vim integration, Nix development tooling, and a Windows Vagrant test environment make up the remainder. The material explicitly identifies the snapshot as a reproduction artifact for a GitHub Actions workflow vulnerability. The exploitable component is `.github/workflows/pr.yml`, specifically the `generate-files` job triggered by `pull_request_target`. It checks out a pull request's attacker-controlled fork/branch, leaves credentials persisted, then invokes `cargo run` repeatedly. Consequently, malicious Rust or Cargo-controlled build/runtime behavior from the PR executes with target-repository workflow credentials. The job then commits generated files and executes `git push`; its `contents: write` permission and lab fallback to `github.token` make this an operational privileged CI code-execution and credential-abuse chain. No malicious callback address, IP, reverse shell, or fixed exfiltration payload is embedded in the snapshot; an attacker would supply their own payload in a pull request.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.