AAK-RUNTIME-ADV-003
Lockfile or exact pin puts a library bundling an affected codec below its fix
| 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-111497, GHSA-9v8h-qqgm-4m35 |
What it catches
CVE-2026-111497 is an out-of-bounds write in Google's Brotli decoder (1.0.3 through 1.2.0) on a crafted stream; CISA added it to KEV on 2026-10-27. Google fixed it in 1.0.10, 1.1.1 and 1.2.1. Python's two Brotli bindings bundle the decoder, and PyPI carries only the 1.2 line's fix:
| Package | Affected | Fixed |
|---|---|---|
Brotli |
from 1.0.3, below 1.2.1 | 1.2.1 |
brotlicffi |
from 1.0.3, below 1.2.1.0 | 1.2.1.0 |
The rule reports a lockfile entry (uv.lock, poetry.lock, Pipfile.lock,
package-lock.json, pnpm-lock.yaml, yarn.lock) or an exact pin
(brotlicffi==1.2.0.2) below the fix. Versions compare on every number, so
brotlicffi's four-part versions are read correctly.
What it does not catch
- A range (
Brotli>=1.0): it does not say which release is installed. - A copy of the decoder vendored in other code, a system
libbrotli, or the copy Node.js bundles (that is AAK-RUNTIME-ADV-001).
How to fix
Upgrade to Brotli 1.2.1 or brotlicffi 1.2.1.0 and re-lock. Until then, do not decompress Brotli data from a source you do not trust.
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
BundledCodecBelowFix
What it detects
A lockfile resolves, or a manifest pins exactly, a library that bundles a codec an advisory in AAK's bundled advisory file covers, below the library's fixed release: Brotli below 1.2.1 or brotlicffi below 1.2.1.0 on PyPI, which bundle the Brotli decoder with CVE-2026-111497 (an out-of-bounds write on a crafted stream, in CISA KEV since 2026-10-27). Google fixed the decoder in 1.0.10, 1.1.1 and 1.2.1; PyPI has only the 1.2 line's fix.
How to fix (registry)
Upgrade to the fixed release (Brotli 1.2.1, brotlicffi 1.2.1.0) and re-lock. Until then, do not decompress Brotli data from a source you do not trust.
To confirm the finding is gone, report only this rule:
agent-audit-kit scan . --rules AAK-RUNTIME-ADV-003
Limitations
Reads uv.lock, poetry.lock, Pipfile.lock, package-lock.json, npm-shrinkwrap.json, pnpm-lock.yaml and yarn.lock (v1) through the pin table's lockfile reader, and the exact pins (==, ===) in requirements*.txt, pyproject.toml, Pipfile and package.json, for the libraries the advisory file names: today PyPI's Brotli (affected from 1.0.3, fixed 1.2.1) and brotlicffi (from 1.0.3, fixed 1.2.1.0). A range is not reported, since it does not say which release is installed, and neither is a copy of the decoder vendored in other code or a system library. A lockfile that resolves one release more than once is reported once, at its first entry. A manifest over 2 MB or a lockfile over 32 MiB is not read.
References
- CVE: CVE-2026-111497
- OWASP MCP Top 10: MCP04:2025 (Software Supply Chain Attacks & Dependency Tampering)
- OWASP Agentic Top 10: ASI04 (Agentic Supply Chain Vulnerabilities), ASI05 (Unexpected Code Execution (RCE))
- Adversa AI MCP Top 25 (AAK-defined ids): ADV-SUPPLY-04 (Known Vulnerable Dep)
- Incidents and advisories: CISA-KEV-2026-10-27-BROTLI
- CSA AI Controls Matrix (AICM): STA-08