Axon: Download of Code Without Integrity Check in axon-mcp
Summary
The axon rtk-install command 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.
Details
The download path lives in src/axon/context/rtk_bootstrap.py:
_http_download()fetches the release archive over HTTPS viaurllib.request.urlopen()and writes the raw response bytes to disk — no hash comparison against any published value._extract_binary()unpacks the archive (zip/tar.gz) and sets the executable bit (out.chmod(... S_IXUSR | S_IXGRP | S_IXOTH)), again with no verification step.- There is no reference to checksum, sha256, verify, signature, gpg, cosign, or sigstore anywhere in this file.
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,
)
PoC
This is a missing-control finding rather than an active exploit, so reproduction is by code audit rather than a live payload:
- Clone
sammyjdev/axonand opensrc/axon/context/rtk_bootstrap.py. - Confirm
_http_download()and_extract_binary()perform no hash/signature check beforechmod +x. - Trace the call chain:
bootstrap_rtkx()→_http_download()→_extract_binary()→rtk_binary_path()(inrtk.py) →subprocess.run()incompress_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.
Impact
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.
What to do
Remediation is not established. Users should inspect the referenced commits in the project repository for relevant security updates.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Python (PyPI) | axon-mcp | <= 0.1.0 | no fix |
References
- https://github.com/sammyjdev/axon/security/advisories/GHSA-r7wg-f7r2-8wf7
- https://nvd.nist.gov/vuln/detail/CVE-2026-76818
- https://github.com/sammyjdev/rtkx/pull/2
- https://github.com/sammyjdev/rtkx/pull/3
- https://github.com/sammyjdev/axon/commit/398e47d5d2b1e1ba88c8d2bac90ac30811a9152b
- https://github.com/sammyjdev/axon/commit/c5863e616688c6c60b2716db9ce4b1b522213b8c
- https://github.com/sammyjdev/axon/commit/d2cc7bccd99c76ec06ac7f7f04d3b2f765c9e741
- https://github.com/sammyjdev/axon
- CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H- Weakness (CWE)
CWE-494- Platform
- Python (PyPI)
- Package
axon-mcp- Disclosed
- 19.11.2026
- Updated
- 20.11.2026 10:00
Sources and licenses · Edited or translated by DockRay; source rights and applicable licenses are retained.
OSV / GitHub Advisory Database - GHSA-r7wg-f7r2-8wf7 - CC BY 4.0
Vulnerability history: axon-mcp
All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.
This is the only known vulnerability of this package.
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.