MCPNews

The Model Context Protocol ecosystem, verified

Current spec 2026-07-28

CVE record: Hermes Agent's bundled MCP catalog pointed at a mutable branch, making a third-party repo compromise an RCE path

VulnCheck published CVE-2026-82021 on 2026-08-28 against NousResearch's Hermes Agent, whose repository shows roughly 239,000 GitHub stars: its bundled MCP catalog referenced a third-party upstream repository by mutable branch rather than pinned commit SHA, so compromising that upstream meant arbitrary code execution for agent users. The fix shipped in v0.19.0 on 2026-07-20, five and a half weeks before the record. A separate VulDB record, CVE-2026-84289, published 2026-09-01, describes uncontrolled memory allocation in the MCP tool lister for 0.18.x and names no fixed version.

VulnCheck published CVE-2026-82021 on 2026-08-28 against Hermes Agent, the NousResearch agent framework whose repository shows roughly 239,000 GitHub stars. The finding is a supply-chain shape rather than a parser bug: the agent's bundled MCP catalog referenced a third-party upstream repository by mutable branch instead of a pinned commit SHA. An attacker who compromised that upstream could ship arbitrary code to every agent that resolved the catalog entry, which the record scores 9.0 critical on CVSS 4.0.

The fix predates the record by five and a half weeks: v0.19.0, released 2026-07-20 under the project's calendar tag v2026.7.20, moved off the mutable reference. The affected range is narrow and exactly stated, 0.18.2 up to that release.

A second record against the same project arrived on 2026-09-01 from VulDB: CVE-2026-84289, a 5.3 medium, describes uncontrolled memory allocation in the list_tools function of tools/mcp_tool.py. It lists 0.18.0 through 0.18.2 as affected and names no fixed version; the project's releases have since moved to v0.21.0. The two records carry different weights, a coordinated CNA disclosure with a shipped fix against a database entry with no vendor response on file, and are best read separately.

Pinning by SHA rather than branch is the standing remedy for consume-a-repo supply chains, and MCP catalogs, which exist to tell agents what code to run, concentrate exactly that risk.

How was this verified, and what are the sources?

Published · last verified · confidence 1.00.

  1. CVE-2026-82021 CNA record (VulnCheck) - "Hermes Agent 0.18.2 < 0.19.0 MCP Catalog Supply Chain RCE via Mutable Branch Reference", CVSS 4.0 9.0 critical / 3.1 8.3 high; affected 0.18.2 before 0.19.0 (calendar tags 2026.7.7.2 before 2026.7.20); published 2026-08-28 - accessed
  2. Hermes Agent v0.19.0 release (tag v2026.7.20), published 2026-07-20 - the fixed version, out five and a half weeks before the record - accessed
  3. CVE-2026-84289 CNA record (VulDB) - uncontrolled memory allocation in list_tools of tools/mcp_tool.py, CVSS 4.0 5.3 medium; lists 0.18.0 through 0.18.2 as affected and names no fixed version; published 2026-09-01 - accessed

← All news