PT-2026-42204 · Crates.Io · Rtk

Published 2026-05-20 · Updated 2026-05-20 · CVE-2026-45792

OSV

CVSS v4.0

6.9

Medium

Base vector

AV:L/AC:L/AT:P/PR:N/UI:A/VC:N/VI:H/VA:N/SC:H/SI:H/SA:N

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.
• SHA-256 hash verification: if the file changes after trust, filters are blocked again until re-reviewed.
• New rtk trust / rtk untrust commands for explicit user consent.
• Trust store implemented in src/trust.rs; trust gate added in src/toml filter.rs.

Fix

Insufficient Verification of Data Authenticity

Untrusted Search Path

Weakness Enumeration

CWE-345

CWE-426

Related Identifiers

CVE-2026-45792

GHSA-FVVM-949W-QJ4W

Affected Products

Rtk

References · 5

• https://osv.dev/vulnerability/GHSA-fvvm-949w-qj4w · Vendor Advisory
• https://github.com/rtk-ai/rtk · Note
• https://github.com/rtk-ai/rtk/security/advisories/GHSA-fvvm-949w-qj4w · Note
• https://github.com/rtk-ai/rtk/pull/625 · Note
• https://github.com/rtk-ai/rtk/pull/623 · Note