rtk
Affected
- introduced
0, fixed0.32.0(semver)
Fixed versions
0.32.0
Fix
- Fixed version
0.32.0cargo update -p rtk --precise 0.32.0
Advisory
Also known as: CVE-2026-45792
RTK improperly trusts project-local filter configuration, allowing silent tampering of command output shown to LLM
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.
Patch
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.Medium Basis: The source's own band: MODERATE
0, fixed 0.32.0 (semver)0.32.0
0.32.0cargo update -p rtk --precise 0.32.0Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0