What is CVE-2026-45792?

CVE-2026-45792 is a medium-severity security vulnerability in rtk (rust), affecting versions < 0.32.0. It is fixed in 0.32.0.

How severe is CVE-2026-45792?

CVE-2026-45792 has a CVSS score of 5.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of rtk are affected by CVE-2026-45792?

rtk (rust) versions < 0.32.0 is affected.

Is there a fix for CVE-2026-45792?

Yes. CVE-2026-45792 is fixed in 0.32.0. Upgrade to this version or later.

Is CVE-2026-45792 exploitable, and should I be worried?

Whether CVE-2026-45792 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-45792 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-45792?

Upgrade rtk to 0.32.0 or later.

CVE-2026-45792 in rtk

Q: How severe is CVE-2026-45792?

CVE-2026-45792 has a CVSS score of 5.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of rtk are affected by CVE-2026-45792?

rtk (rust) versions < 0.32.0 is affected.

Q: Is there a fix for CVE-2026-45792?

Yes. CVE-2026-45792 is fixed in 0.32.0. Upgrade to this version or later.

Q: Is CVE-2026-45792 exploitable, and should I be worried?

Whether CVE-2026-45792 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-45792 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-45792?

Upgrade rtk to 0.32.0 or later.

Summary

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.

Impact

CVE-2026-45792 has a CVSS score of 5.5 (Medium). The vector is requires local access, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.32.0); upgrading removes the vulnerable code path.

Affected versions

rtk (< 0.32.0)

Security releases

rtk → 0.32.0 (rust)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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.

Frequently Asked Questions

What is CVE-2026-45792? CVE-2026-45792 is a medium-severity security vulnerability in rtk (rust), affecting versions < 0.32.0. It is fixed in 0.32.0.
How severe is CVE-2026-45792? CVE-2026-45792 has a CVSS score of 5.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of rtk are affected by CVE-2026-45792? rtk (rust) versions < 0.32.0 is affected.
Is there a fix for CVE-2026-45792? Yes. CVE-2026-45792 is fixed in 0.32.0. Upgrade to this version or later.
Is CVE-2026-45792 exploitable, and should I be worried? Whether CVE-2026-45792 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-45792 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-45792? Upgrade rtk to 0.32.0 or later.