CVE-2026-45792Medium· 5.5▾ SunlitRTK improperly trusts project-local filter configuration, allowing silent tampering of command output shown to LLM
▾ Sunlit zone — Low / medium · no exploitation signal
impact 30.3 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Jul 21.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
0.08%
0.08% → 0.1%
RTK (Rust Token Killer) improperly trusts project-local configuration files. In versions prior to 0.32.0, RTK automatically loads .rtk/filters.toml from the working directory with highest priority and without user notification. An attacker can place a malicious filter file in a repository to apply regex-based modifications (e.g., strip_lines_matching) to shell command output before it is shown to the LLM, without any indication that the output has been modified.
This allows attackers to selectively suppress or alter command output (including file contents, diffs, and security scan results) without detection, potentially concealing malicious code during AI-assisted development or review.
Fixed in v0.32.0 (PRs #623, #625):
.rtk/filters.toml is now blocked by default when untrusted, with a visible warning: [rtk] WARNING: untrusted project filters — Filters NOT applied. Run rtk trust to review and enable.rtk trust / rtk untrust commands for explicit user consent.src/trust.rs; trust gate added in src/toml_filter.rs.rtk < 0.32.0Upgrade to a patched release:
rtk 0.32.0