Skip to content

AAK-KNOWN-VULN-002

A launched MCP server, binary or image is a release a published advisory lists as affected

Field Value
Severity The advisory's for a launch whose release is in its range: CRITICAL from CVSS 9.0, HIGH from 7.0, MEDIUM below that; MEDIUM for a launch whose release could not be read
Category SUPPLY_CHAIN
Shipped v0.6.30
Scanner agent_audit_kit/scanners/known_vulns_launch.py
Feed the launch list of agent_audit_kit/advisory_feed.py, filled by agent_audit_kit/nvd_feed.py
OWASP MCP MCP04:2025 (Software Supply Chain Attacks & Dependency Tampering)
OWASP Agentic ASI04 (Agentic Supply Chain Vulnerabilities)

Why it exists

AAK-KNOWN-VULN-001 checks the releases a project installs from PyPI and npm against the advisory feed. Plenty of MCP servers and agent apps are on neither registry: a Go binary a config starts by its path, a module started with go run, an image a compose file pins. On 30 Oct 2026 NVD published two critical records of that kind. MoLing, a Go MCP server, took no authentication on its SSE endpoints before 0.5.0 (CVSS 9.6). TAKO, an Okta agent app shipped as a Docker Hub image, let anyone create its first administrator before 3.0.1-beta (CVSS 9.8). Each record names a vendor and a product and no package, so no package row could map it, and a project that ran MoLing 0.4.0 from .mcp.json passed every rule.

This rule reads what a project launches and matches it against those records, through reviewed launch rows that say how each project starts its software.

What it catches

A launch of software a launch row names, in a release the record lists as affected:

  • in a JSON MCP client config (.mcp.json, .vscode/mcp.json, .cursor/mcp.json, claude_desktop_config.json and every other *mcp*.json), any server of mcpServers or VS Code's servers:
  • its command, by file name: /usr/local/bin/moling and C:\tools\moling.exe are both moling;
  • go run <module>@<version>, the module matched at a path boundary, so a package inside it (github.com/gojue/moling/cli) counts and github.com/gojue/molingx does not;
  • the image a docker, podman or nerdctl run starts, also spelled docker.io/... for a Docker Hub image;
  • an argument that is itself a github.com/<owner>/<repo> URL, with the release its @v1.2.3, #v1.2.3, /releases/tag/, /releases/download/, /tree/ or /archive/ part names;
  • any of these behind sh -c, bash -c, cmd /c or PowerShell's -Command, two levels deep;
  • in YAML files (compose files, Kubernetes manifests, Helm values) and Dockerfiles, a reference to a launch row's image where an image goes: an image: value, a FROM line, a quoted string, or a Helm repository with its tag. A commented-out line is skipped.

A launch whose release is in the advisory's range is reported at the advisory's severity. A launch that names no release AAK can read is MEDIUM, and the finding says why: a bare command, latest, an untagged or digest-only image, a branch or a commit. A launch whose release is outside the range is quiet. One finding per file and advisory, at the first launch in its range (counting the others), else at the first one whose release could not be read.

The launch rows

The rows live beside the package rows in agent_audit_kit/data/cna_package_map.json, under launch. Each names a project by its repository and by the vendor and product its CNA writes, and lists the names a project starts it by. Every name comes from the project's own repository, never from a name alone:

Software Read from commands go_modules images
gojue/moling README ("command": "/usr/local/bin/moling"), go.mod moling github.com/gojue/moling none (no Dockerfile or compose file; the README calls MoLing dependency-free)
fctr-id/okta-ai-agent (TAKO) docker-compose.yml none none fctrid/ai-agent-for-okta

An NVD record maps to a row by the CNA's repository, else by its vendor and product, as a package row maps one. aak update reads the matching records into the feed's launch list and prints the ten (vendor, product) pairs that most often mapped to nothing, so the next rows come from evidence.

How a release is read

As semver 2.0 with a leading v dropped, the order GitHub writes these ranges in. A Go pseudo-version is a pre-release of the release after it, so a commit after 0.4.0 reads as 0.4.1-something and stays in a < 0.5.0 range. TAKO's releases are named -beta, and its own compose file at the fixed tag runs the image tag 3.0.1-alpha, which Docker Hub received an hour before the fix commit: semver puts 3.0.1-alpha below 3.0.1-beta, and reports it.

A two-part tag or Go query (3.1, @v0.4) floats over its line. It is reported at the advisory's severity when every release on the line is affected, is quiet when none is, and is MEDIUM when the line holds both.

What it does not see

  • Software no launch row names. Two rows exist on 31 Oct 2026; a record that maps to no row is counted and dropped.
  • A launch outside an MCP config or an image reference: a shell script, a Makefile, a systemd unit, or a YAML MCP config's command (a YAML file is read for image references only).
  • An argument that only links into a repository (/blob/...), and a GitHub shorthand such as github:owner/repo.
  • An image tag's suffix is a semver pre-release, so a variant tag of the first fixed release (1.2.3-alpine for a fix in 1.2.3) reads affected.
  • The feature in use: MoLing's flaw is in its SSE mode (-l), and a stdio launch of 0.4.0 is reported all the same, because the release is the flawed one.
  • A file over 2 MB.

How to fix

Pin the launch to a release outside the advisory's range, the fix the finding names or later: go run module@vX.Y.Z, an image tag naming the release, or the binary's release. Then restart the server or redeploy. For a launch AAK could not read, check which release it runs and pin it. Where the advisory lists no fixed release, stop running the software or keep the flawed component unreachable. Run aak update so the scan reads the current NVD records rather than the bundled few.

The records that showed the gap, as NVD listed them on 2026-10-31. They are context, not this rule's references: the rule reports whatever launch entry the feed holds.

Software CVE CNA range Fixed In the bundled feed
MoLing, SSE endpoints with no authentication CVE-2026-62863 < 0.5.0 0.5.0 yes (CVSS 3.x 9.6)
TAKO, unauthenticated first-administrator setup CVE-2026-63377 < 3.0.1-beta 3.0.1-beta yes (CVSS 3.x 9.8)
TAKO, any signed-in user runs Python CVE-2026-63378 < 3.0.1-beta 3.0.1-beta yes (CVSS 3.x 8.8)

A finding on the MoLing one reads:

`go run github.com/gojue/moling@v0.4.0` in .mcp.json launches gojue/moling v0.4.0, which
CVE-2026-62863 (NVD CNA record, CVSS 3.x 9.6) lists as affected; it is fixed in 0.5.0
(https://nvd.nist.gov/vuln/detail/CVE-2026-62863).

Registry reference

This section is generated from the rule registry (agent_audit_kit/rules/builtin.py) when the documentation is built, so it follows the scanner. The rest of the page is hand-written; where the two disagree, the registry is what runs.

Severity
CRITICAL
Category
Supply Chain (supply-chain)
Scanner
agent_audit_kit/scanners/known_vulns_launch.py
Auto-fixable
No.
SARIF name
KnownVulnerableLaunch

What it detects

An MCP client config starts, or a compose file, Kubernetes manifest, Helm values file or Dockerfile runs, a release of software that an NVD record's CNA data lists as affected, where the software is on neither PyPI nor npm: a binary an MCP config names as its command, a Go module it starts with go run, an image it starts with docker run or a deployment file pins, or its GitHub repository given as an argument. On 0.6.29 a project whose .mcp.json ran MoLing 0.4.0, a Go MCP server whose SSE endpoints took no authentication before 0.5.0 (CVSS 9.6), passed every rule: NVD's record named no package for AAK-KNOWN-VULN-001 to map, only a vendor and a product. The advisory feed now maps such records through reviewed launch rows, each naming how the project's own repository says to start the software, and this rule matches them against what a project starts. The finding carries the record's severity for a launch that names a release in its range, and is MEDIUM for one whose release could not be read.

How to fix (registry)

Pin the launch to a release outside the advisory's range (the fix the finding names, or later): go run module@vX.Y.Z, an image tag naming the release, or the binary's release, then restart the server or redeploy. For a launch AAK could not read, check which release it runs and pin it. Where the advisory lists no fixed release, stop running it or keep the flawed component unreachable. Run aak update so the scan reads the current NVD records rather than the bundled few.

To confirm the finding is gone, report only this rule:

agent-audit-kit scan . --rules AAK-KNOWN-VULN-002

Limitations

Matches only software a reviewed launch row of data/cna_package_map.json names (MoLing and TAKO on 31 Oct 2026), and maps an NVD record to a row only by the CNA's repository or its vendor and product, never by a name alone; a record no row maps is counted by aak update and dropped. Reads, outside AAK's skip directories, the JSON MCP client configs container_image_pins reads (*mcp*.json, claude_desktop_config.json), parsed as JSONC: a server's command by its file name, go run <module>@<version>, a docker, podman or nerdctl run, an argument that is itself a github.com/<owner>/<repo> URL (a link into the repository is not a launch), and a command line behind sh -c, bash -c, cmd /c or -Command, two levels deep. In YAML files and Dockerfiles it reads image references only, where an image goes (an image: value, a FROM line, a quoted string, a Helm repository and tag), so a YAML MCP config's command, a shell script, a Makefile and a systemd unit are not read. A release is read as semver 2.0 with a leading v dropped, so an image tag's suffix is a pre-release: 1.2.3-alpine sorts below 1.2.3, and a variant tag of the first fixed release reads affected. A two-part tag (3.1) is reported at the record's severity only when every release on its line is affected. A launch that names no release (a bare command, latest, an untagged or digest-only image, a branch, a commit) is MEDIUM. The rule reports the release, not whether the launch uses the flawed feature: MoLing's flaw is in its SSE mode, and a stdio launch of 0.4.0 is reported too. One finding per file and advisory; where another rule reports every CVE id of the advisory on the same line of the same file at or above this finding's severity, only that rule's finding is kept. The bundled launch entries are NVD's three records of 30 Oct 2026 against MoLing and TAKO, so without aak update nothing else is known. A file over 2 MB is not read.

References


All rules.