Skip to content

AAK-RUNTIME-ADV-001

Declared Node.js, PHP or Python runtime below the fixed release on its line

Field Value
Severity CRITICAL (from the advisory; a KEV entry is CRITICAL)
Category SUPPLY_CHAIN
Shipped v0.6.28
Scanner agent_audit_kit/scanners/runtime_advisories.py
OWASP MCP MCP04:2025 (Software Supply Chain Attacks & Dependency Tampering)
OWASP Agentic ASI04 (Agentic Supply Chain Vulnerabilities), ASI05 (Unexpected Code Execution)
CVE CVE-2026-109618, CVE-2026-109619 (PHP2Shell), CVE-2026-111497 (Brotli in Node.js)

What it catches

A runtime release that an advisory in AAK's bundled advisory file covers, named anywhere the project states which runtime it runs:

Where Example that fires
Dockerfile FROM (official node, php, python images) FROM node:24.22.0-slim, FROM php:8.4.26-fpm
Version files .nvmrc 22.23.3, .tool-versions nodejs 20.19.0
engines.node in package.json ">=18", judged at 18.0.0, the lowest release it admits
Managed runtimes runtime: nodejs20 (app.yaml), runtime: nodejs18.x (serverless.yml)
MCP server launchers "command": "~/.nvm/versions/node/v24.22.0/bin/node"

A release is judged against the fixed release on its own line: the major for Node.js, major.minor for PHP and Python. A line that got no fixed release (an end-of-life line, such as Node.js 20 or PHP 8.1) is affected at every patch, and the evidence gives its end-of-life date from endoflife.date.

The advisories bundled with v0.6.28

Advisory Runtime Fixed in KEV
CVE-2026-109618, PHP2Shell (OOM corruption) PHP from 7.3.0 8.2.35, 8.3.36, 8.4.27, 8.5.12 added 2026-10-26, due 2026-10-29
CVE-2026-109619, PHP2Shell (stale global state) PHP from 5.4.0 8.2.35, 8.3.36, 8.4.27, 8.5.12 added 2026-10-26, due 2026-10-29
CVE-2026-111497, Brotli decoder Node.js from 10.16.0 and 11.7.0 22.23.4, 24.22.1, 26.12.1 added 2026-10-27, due 2026-11-10

The file is agent_audit_kit/data/runtime_advisories.json; each entry records its source URL and the date it was read. A copy at ~/.agent-audit-kit/runtime_advisories.json is read first. A scan never fetches it. No Python advisory is in the file, so a Python runtime is read and reported by nothing today.

What it does not catch

  • An image pinned by digest alone, an image built from an earlier stage, and images from other publishers (bitnami/node, cimg/node).
  • A version set through an ARG without a default, or outside the files above (a CI job's setup-node, a shell).
  • What actually runs: engines.node says what a package supports, and a managed runtime's patch release is the platform's.

How to fix

Move to the fixed release on the same line, or to a supported line that has one, and pin the full version or the image digest. An end-of-life line gets no fix: upgrade the line, then rebuild every image built on the old base.


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/runtime_advisories.py
Auto-fixable
No.
SARIF name
RuntimeBelowAdvisoryFix

What it detects

A Dockerfile FROM, a version file (.nvmrc, .node-version, .python-version, .tool-versions), engines.node, a managed runtime (runtime: in app.yaml or serverless.yml) or an MCP server's launcher path names a runtime release that an advisory in AAK's bundled advisory file covers: below the fixed release on its line, or on a line that got no fixed release. PHP2Shell (CVE-2026-109618 and CVE-2026-109619, remote code execution, fixed in PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12) and CVE-2026-111497 (an out-of-bounds write in the Brotli decoder Node.js bundles, fixed in 22.23.4, 24.22.1 and 26.12.1 only) are in CISA's Known Exploited Vulnerabilities catalog. Node.js's security release of 11 Nov 2026 (16 CVEs, seven rated high, in HTTP/2, HTTPS and TLS) is in the file too, fixed in 22.23.5, 24.22.3 and 26.13.1. No dependency pin sees them: the version that matters is the interpreter an MCP server runs on.

How to fix (registry)

Move to the fixed release on the same line (PHP 8.4.27, Node.js 24.22.3 and so on) or to a supported line that has one, and pin the full version (or the image digest) so the next fix is a visible change. An end-of-life line gets no fix: upgrade the line. Rebuild images after changing the base.

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

agent-audit-kit scan . --rules AAK-RUNTIME-ADV-001

Limitations

Judges a runtime against data/runtime_advisories.json, or a copy at ~/.agent-audit-kit/runtime_advisories.json, read first; a scan never fetches it. The bundled file names PHP (CVE-2026-109618 from 7.3.0, CVE-2026-109619 from 5.4.0) and Node.js (CVE-2026-111497 from 10.16.0, 11.7.0 on the 11 line; the 11 Nov 2026 security release as one entry, NODEJS-SEC-2026-11-11, its 16 CVEs as aliases, with no first affected release, since Node.js says end-of-life versions are always affected, and HIGH for every line, though three high CVEs reach only 24.x and 26.x) and no Python advisory, so a Python runtime is read and reported by nothing today. A release is judged against the fixed release on its line (the major for Node.js, major.minor for PHP and Python); a line with no fixed release is affected when it is older than the newest fixed line, and a newer line is taken to carry the fix. Reads the FROM of Dockerfiles and Containerfiles naming the official node, php or python image (Docker Hub, mirror.gcr.io/library or public.ecr.aws/docker/library), with global ARG defaults filled in; an image pinned by digest alone, a stage built from another, and other publishers' images (bitnami/node) are not judged. Reads .nvmrc and .node-version (first line), .python-version and .tool-versions (every version listed), engines.node, judged at the lowest release the range admits, which says what the package supports and not what runs, runtime: in app.yaml and serverless.yml (a line with no fix is reported, a managed line with one is AAK-RUNTIME-ADV-002), and an MCP server's command or argument under an nvm, asdf, mise, Volta, fnm, n, pyenv or Homebrew Cellar path that carries a version. Reports one finding per declaration, at the most severe advisory's severity (CRITICAL for a KEV entry). A FROM reference that runs past 1,024 characters with its ARGs filled in is not judged, and a value repeated on one line is judged once. A file over 1 MB is not read.

References


All rules.