{"answers":{"affected":"2 open source packages ship an affected version, including rtk. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45792 exists.","fix":"Upgrade rtk to 0.32.0 or later.","what":"CVE-2026-45792 is a medium-severity vulnerability in rtk-ai rtk, published on 23 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-45792 and fix it if it is affected.\n\nWhat it is: CVE-2026-45792 is a medium-severity vulnerability in rtk-ai rtk, published on 23 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45792 exists.\n\nAffected packages and fixed versions:\n- rtk (crates.io): affected all versions; fixed in 0.32.0\n- rtk (crates.io): affected all versions; fixed in 0.32.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-45792/ (Markdown: https://insights.sbomify.com/CVE-2026-45792/index.md)","id":"CVE-2026-45792","markdown":"https://insights.sbomify.com/CVE-2026-45792/index.md","name":"CVE-2026-45792","record":{"aliases":["GHSA-fvvm-949w-qj4w"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Rust token killer tool","requires_auth":"none","summary":"Attackers can tamper with command output shown to LLMs via malicious project-local config files, concealing malicious code during AI-assisted development.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"rtk","vendor":"rtk-ai"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:A/VC:N/VI:H/VA:N/SC:H/SI:H/SA:N","version":"4.0"},"cwes":[{"id":"CWE-426","name":"Untrusted Search Path"},{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"rtk filters and compresses command outputs before they reach your LLM context. Prior to 0.32.0, RTK (Rust Token Killer) improperly trusts project-local configuration files. 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. This vulnerability is fixed in 0.32.0.","ecosystems":["crates.io"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"RTK improperly trusts project-local filter configuration, allowing silent tampering of command output shown to LLM","id":"CVE-2026-45792","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"other","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Composer: Github Actions issued GITHUB_TOKEN disclosure in GitHub Actions logs","id":"CVE-2026-45793"},"packages":[{"ecosystem":"crates.io","fixed":["0.32.0"],"introduced":["0"],"last_affected":[],"package":"rtk","purl":null,"source":"GHSA-fvvm-949w-qj4w"},{"ecosystem":"crates.io","fixed":["0.32.0"],"introduced":["0"],"last_affected":[],"package":"rtk","purl":"pkg:cargo/rtk","source":"GHSA-fvvm-949w-qj4w"}],"prev":{"headline":"Dokploy: Password Change Does Not Revoke Active Sessions","id":"CVE-2026-45791"},"products":["rtk"],"published":"2026-06-23","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-26","vendors":["rtk-ai"]},"summary":"Attackers can tamper with command output shown to LLMs via malicious project-local config files, concealing malicious code during AI-assisted development.","url":"https://insights.sbomify.com/CVE-2026-45792/"}