Axon MCP tool runs downloaded binary with no integrity check
A GitHub advisory says the axon-mcp Python package fetches and executes a helper binary from GitHub releases without checking any checksum or signature.
By The Agentic Times ·

A security advisory published on 19 November 2026 says the Python package axon-mcp, from the developer sammyjdev, downloads a pre-built binary from GitHub releases and runs it without verifying that the file is genuine. The advisory, GHSA-r7wg-f7r2-8wf7, is tracked as CVE-2026-76818 and classifies the issue as CWE-494, download of code without integrity check.
According to the advisory, the problem sits in the tool's bootstrap code at src/axon/context/rtk_bootstrap.py. A function named _http_download() fetches a release archive over HTTPS and writes the raw bytes to disk, with no comparison against any published hash. A second function, _extract_binary(), unpacks the zip or tar.gz archive and sets the executable bit on the result. The advisory states there is no mention of a checksum, sha256, verification step, signature, GPG, cosign or sigstore anywhere in that file.
The downloaded file is not left idle. The advisory traces the call chain from bootstrap_rtkx() through the download and extraction steps to rtk_binary_path() in src/axon/context/rtk.py, which resolves to the bootstrapped binary at ~/.axon/bin/rtkx. A function called compress_text_with_rtk() then invokes that binary directly through subprocess.run() on every text-compression call. In other words, the unverified executable runs as part of normal operation rather than on a rare code path.
The advisory is clear that this is a missing control rather than a live exploit. Nobody is described as having tampered with the binary. The risk it describes is conditional: if the release pipeline for the sammyjdev/rtkx repository, or a maintainer's release credentials, were ever compromised, then 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. That outcome is described as potential arbitrary code execution.
Affected users are described as anyone who runs the axon rtk-install command or who triggers the automatic bootstrap. The advisory lists the affected package as pip/axon-mcp.
Because there is no active payload, the advisory sets out reproduction steps by code audit rather than exploitation. It suggests cloning the sammyjdev/axon repository, opening rtk_bootstrap.py and confirming that neither the download nor the extraction function performs a hash or signature check before making the file executable. It also offers a safe demonstration of impact: the module's own docstring notes that the download step is injectable so that the extraction logic can be tested offline, and the advisory says a tester can point the download callable at a local HTTP server serving an attacker-controlled archive and confirm that the archive is extracted, marked executable and run without rejection.
The pattern matters for agent tooling because helper binaries pulled down at install time often inherit the full privileges of the agent runtime that calls them. The advisory frames the missing verification as the removal of the last line of defence against a supply-chain compromise of the binary dependency, rather than a flaw that can be exploited today on its own.
The advisory does not list a fixed version, and the incident record derived from it shows the issue as reported. No comment from the maintainer appears in the advisory.
Sources
- github.comhttps://github.com/advisories/GHSA-r7wg-f7r2-8wf7
