Output tampering via untrusted project-local filters
Published Jun 23, 2026 · Updated Jun 23, 2026
Improper configuration trust in RTK before 0.32.0 allows local users to tamper with LLM-visible command output through a crafted repository. RTK loads .rtk/filters.toml from the working directory at highest priority without notice, then applies its regex rules to command output. Exploitation requires an operator or AI agent to run RTK inside an attacker-controlled checkout, allowing file, diff, and scan output to be suppressed or rewritten.
Summary
What happened
Improper configuration trust in RTK before 0.32.0 allows local users to tamper with LLM-visible command output through a crafted repository. RTK loads .rtk/filters.toml from the working directory at highest priority without notice, then applies its regex rules to command output. Exploitation requires an operator or AI agent to run RTK inside an attacker-controlled checkout, allowing file, diff, and scan output to be suppressed or rewritten.
The record
- CVE
- CVE-2026-45792
- Published
- Jun 23, 2026
- Updated
- Jun 23, 2026
- Vendor
- RTK AI Labs
- Product
- RTK
- Classifications
- CWE-426, CWE-345, T1564
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 23, 2026CVE publishedPublication date reported by the CVE source.
- Jun 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.32.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Malicious project-local filter configuration exampleproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo