CVE-2026-76818

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-11-19. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-129310 (ENISA EUVD) · GHSA-r7wg-f7r2-8wf7 (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5HIGHhigh confidence
EG Risk
65
EG Risk 65/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.2%
EPSS %ILE
4th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-19). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 18, 2026

Last Modified

November 19, 2026

Advisory Details (6)

Auto-updated Nov 18, 2026
Patch available. Sources: github, github_commit, github_pr.
GitHub commit

commit d2cc7bccd99c (sammyjdev/axon)

Fix landed in sammyjdev/axon commit d2cc7bccd99c — awaiting tagged release

https://github.com/sammyjdev/axon/commit/d2cc7bccd99c76ec06ac7f7f04d3b2f765c9e741
GitHub commit

commit c5863e616688 (sammyjdev/axon)

Fix landed in sammyjdev/axon commit c5863e616688 — awaiting tagged release

https://github.com/sammyjdev/axon/commit/c5863e616688c6c60b2716db9ce4b1b522213b8c
GitHub commit

commit 398e47d5d2b1 (sammyjdev/axon)

Fix landed in sammyjdev/axon commit 398e47d5d2b1 — awaiting tagged release

https://github.com/sammyjdev/axon/commit/398e47d5d2b1e1ba88c8d2bac90ac30811a9152b
GitHub pull request Patch Available

fix: package rtk binary as rtkx in release archives (unblocks GHSA-r7wg-f7r2-8wf7 attestation)

Patch available: sammyjdev/rtkx dev-0.43.1-rc.7 (PR #3 merged 2026-07-09)

https://github.com/sammyjdev/rtkx/pull/3
GitHub pull request Patch Available

security: attest build provenance for release artifacts (GHSA-r7wg-f7r2-8wf7)

Patch available: sammyjdev/rtkx dev-0.43.1-rc.7 (PR #2 merged 2026-07-09)

https://github.com/sammyjdev/rtkx/pull/2
GitHub advisoryMentions a patch (unverified)

Download of Code Without Integrity Check in axon-mcp · Advisory · sammyjdev/axon · GitHub

https://github.com/sammyjdev/axon/security/advisories/GHSA-r7wg-f7r2-8wf7

Vendor Advisories for CVE-2026-76818(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipaxon-mcp—ghsa

These rows come from GitHub (GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
axon-mcp0.1.0
  • every version through 0.1.0: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 7× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-22 07:26 UTCOSV refresh
  2. 2026-11-21 16:41 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  3. 2026-11-20 16:38 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  4. 2026-11-19 20:46 UTCEchelonGraph re-scored
  5. 2026-11-19 20:46 UTCGHSA enrichmentGHSA-r7wg-f7r2-8wf7 · GitHub severity HIGH · GitHub CVSS 7.5
  6. 2026-11-19 20:29 UTCEchelonGraph re-scored
  7. 2026-11-19 19:42 UTCEchelonGraph re-scored
  8. 2026-11-19 19:34 UTCEchelonGraph re-scored
  9. 2026-11-19 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  10. 2026-11-18 23:03 UTCENISA EUVD ID recordedEUVD-2026-129310 · Source: ENISA EUVD
  11. 2026-11-18 22:28 UTCEchelonGraph re-scored
  12. 2026-11-18 21:48 UTCEchelonGraph re-scoredFirst assessed: 7.5 HIGH
  13. 2026-11-18 21:47 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-76818?
CVE-2026-76818 is a high-severity vulnerability; its CVE record was published on November 18, 2026. 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,…
When was the CVE record for CVE-2026-76818 published?
The CVE record for CVE-2026-76818 was published on November 18, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 19, 2026; the record at its source may have been updated since.
Is CVE-2026-76818 actively exploited?
CVE-2026-76818 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-76818?
CVE-2026-76818 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-76818?
A fix for CVE-2026-76818 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-76818 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-76818

Explore →

Is Your Infrastructure Affected by CVE-2026-76818?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.