Vulnerability in rtk (CVE-2026-45792)
Summary
Vulnerability in rtk (CVE-2026-45792). Data can be tampered with by attackers. Exploitable via strip_lines_matching. Mitigation: upgrade to 0.32.0 or later.
Original description
The description as published by the source.
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.tomlis 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 untrustcommands for explicit user consent. - Trust store implemented in
src/trust.rs; trust gate added insrc/toml_filter.rs.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-45792 has been found in rtk.
Attackers can target a specific entry point like strip_lines_matching over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 5.5/10.
What to do: upgrade rtk to 0.32.0 or later.
If unsure, ask your IT team or search "rtk CVE-2026-45792" on the vendor's site.
CVE-2026-45792 (rtk) — CWE-345 / CVSS v3 5.5
Attack vector: local / unauthenticated
Attack surface: strip_lines_matching
Patched: 0.32.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-345) exists in rtk. Attackers reach the vulnerable code path via strip_lines_matching without authentication.
Check the vendor advisory for the affected versions of rtk. Attack surface: strip_lines_matching.
Severity: Medium (CVSS 5.5/10). Data can be tampered with by attackers.
Update to 0.32.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'rtk' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'rtk' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
rtkを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade rtk to 0.32.0ステージング環境で 0.32.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com