Skip to main content
Menu
CVEs

CVE

Axon code execution via unchecked rtkx binary download

Affects Axon users who run 'axon rtk-install' or trigger auto-bootstrap of rtkx, which downloads the rtkx binary without an integrity check. Fixed in Axon 0.1.1.

CVE-2026-76818Published Updated Summary written by a model

7.5HighCNA
Exploited
No known exploitation
Fix
Fixed in 0.1.1
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Axon user runs 'axon rtk-install' or triggers auto-bootstrap of rtkx The sammyjdev/rtkx release pipeline or a maintainer's release credentials are compromised

Summary

Axon (axon-mcp) downloads a prebuilt rtkx binary without checking its checksum, signature, or build attestation. An attacker who compromises the rtkx release pipeline or maintainer credentials could supply a modified binary that runs with Axon's process privileges. The attack can be launched remotely without logging in, but it requires a user to install or automatically bootstrap rtkx.

Original description

Axon is an agent-agnostic context engine that gives AI coding agents continuous memory across sessions, tools, and machines. Prior to 0.1.1, rtk-install in src/axon/context/rtk_bootstrap.py uses _http_download() to fetch a prebuilt rtkx release archive and _extract_binary() to mark it executable, after which compress_text_with_rtk() invokes it without verifying a checksum, signature, or build attestation. If the sammyjdev/rtkx release pipeline or maintainer release credentials are compromised, an attacker can supply a modified binary that executes with the Axon process privileges when a user installs or automatically bootstraps rtkx. This issue is fixed in version 0.1.1.

Who should check

Teams running axon (axon-context-mcp on pip) at version 0.1.0 or earlier that run rtk-install or auto-bootstrap of rtkx

“axon rtk-install downloads a pre-built rtkx binary from GitHub releases”

github.com

cve.now Index

20Pcve.now Index 20 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure12/25Specific setups only, reachable over the network without a login
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.5/10CVSS 7.5
  • No patch0/5No signal

What would change the score

  • Would score about 70 if added to CISA KEV
  • Would score about 65 if CISA's SSVC rates exploitation active

What to do

  • Check whether your setup matches what the bug needs.

    Axon user runs 'axon rtk-install' or triggers auto-bootstrap of rtkx The sammyjdev/rtkx release pipeline or a maintainer's release credentials are compromised
  • Upgrade to a fixed version: 0.1.1.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-76818 (Axon: Download of Code Without Integrity Check in axon-mcp), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-76818 (entry last updated 2026-11-18):
Affected:
- sammyjdev axon: fixed in 0.1.1
Fixed versions: 0.1.1.
Conditions (all must be true for the bug to be hit):
- Axon user runs 'axon rtk-install' or triggers auto-bootstrap of rtkx (source: https://github.com/sammyjdev/axon/security/advisories/GHSA-r7wg-f7r2-8wf7)
- The sammyjdev/rtkx release pipeline or a maintainer's release credentials are compromised (source: https://github.com/sammyjdev/axon/security/advisories/GHSA-r7wg-f7r2-8wf7)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-76818 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-76818 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/sammyjdev/axon/security/advisories/GHSA-r7wg-f7r2-8wf7
- 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
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-76818
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-76818"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • sammyjdev axon

    fixed in 0.1.1

Evidence 8

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-76818

Is CVE-2026-76818 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

Axon downloads the rtkx binary without checking its integrity, so a modified rtkx binary could be run. That could allow arbitrary code execution with the privileges of the axon process.Source: github.com

Which versions are affected by CVE-2026-76818?

axon: before 0.1.1.Source: cve.now feed data

Am I affected, and how do I check?

The listed fixed version is 0.1.1, so Axon versions before 0.1.1 are in range. The relevant setup is running 'axon rtk-install' or triggering auto-bootstrap of rtkx, so check the installed Axon version against 0.1.1 and whether that setup is used.Source: github.com

How do I fix CVE-2026-76818?

Upgrade Axon to 0.1.1 or later, which is the listed fixed version. No vendor patch identifiers are given for this vulnerability.Source: github.com

More CVEs