axon rtk-install downloads a pre-built rtkx binary from GitHub releases and executes it via subprocess.run() on every text-compression call, without verifying its integrity — no checksum, signature, or attestation check anywhere in the download/install path. If the release pipeline or a maintainer token for sammyjdev/rtkx were ever compromised, every axon user who installs or auto-bootstraps rtkx would silently download and execute an unverified binary with the same privileges as the axon process.
The download path lives in src/axon/context/rtk_bootstrap.py:
The binary is not dead code — it's on the active execution path. src/axon/context/rtk.py::rtk_binary_path() resolves to the bootstrapped binary at ~/.axon/bin/rtkx, and compress_text_with_rtk() invokes it directly:
result = subprocess.run( [path, "read", str(tmp_path)], capture_output=True, text=True, timeout=timeout_seconds, )
This is a missing-control finding rather than an active exploit, so reproduction is by code audit rather than a live payload:
Clone sammyjdev/axon and open src/axon/context/rtk_bootstrap.py. Confirm _http_download() and _extract_binary() perform no hash/signature check before chmod +x. Trace the call chain: bootstrap_rtkx() → _http_download() → _extract_binary() → rtk_binary_path() (in rtk.py) → subprocess.run() in compress_text_with_rtk(). Optionally demonstrate impact safely: point download_url() / the download callable (already injectable per the module's own docstring, "the download step is injectable so the extraction logic is testable offline") at a local HTTP server serving an attacker-controlled archive, and confirm it gets extracted, chmod +x'd, and executed with no rejection.
Type: CWE-494 (Download of Code Without Integrity Check), leading to potential arbitrary code execution. Who's affected: Any axon user who runs axon rtk-install or triggers auto-bootstrap, if sammyjdev/rtkx's release pipeline or a maintainer's release credentials are ever compromised. Not exploitable today without that precondition, but the missing control removes the last line of defense against a supply-chain compromise of the binary dependency.
{
"cwe_ids": [
"CWE-494"
],
"github_reviewed": true,
"github_reviewed_at": "2026-11-19T20:34:53Z",
"nvd_published_at": "2026-11-18T22:17:24Z",
"severity": "HIGH"
}