AAK-MCP-DJUST-CVE-2026-113731-001: djust 0.9.0 to 1.2.3: the find_handlers_for_template MCP tool reads any absolute path
- Severity
- LOW
- Category
- Supply Chain (
supply-chain) - Scanner
agent_audit_kit/scanners/mcp_cve_pins_2026_07.py- Auto-fixable
- No.
- SARIF name
DjustMcpTemplatePathRead
What it detects
djust (PyPI djust), a server-side rendering framework for Django, ships an MCP server (python manage.py djust_mcp) whose find_handlers_for_template tool takes a template_path and, when it is an existing absolute path, reads it without checking that it lies under the project or a configured template directory. A client of the server can use the tool to learn whether a file the djust process can read exists, and to get back the parts of it that match the tool's dj-click, dj-submit, dj-change, dj-input, dj-keydown or dj-keyup attribute pattern (CVE-2026-113731, CVSS 3.1 3.3, CWE-22, GHSA-r57g-mc79-8hj2). The maintainer's assessment is that the server speaks stdio as the same user, with no network listener, and that the tool returns no raw file contents. Checked in the PyPI sdists: the tool first ships in 0.9.0 (0.4.4, the release before it, has none), and 1.0.10, 1.1.7, 1.2.4 and 1.3.0rc8 resolve the path and keep it inside the template roots, which 1.0.9, 1.1.6, 1.2.3 and 1.3.0rc7 do not.
How to fix
Upgrade djust to 1.0.10, 1.1.7, 1.2.4 or 1.3.0 or later, on the line you run, and pin it. Until then, connect the djust MCP server only to clients and agents you would let read the files its process can read.
To confirm the finding is gone, report only this rule:
agent-audit-kit scan . --rules AAK-MCP-DJUST-CVE-2026-113731-001
Limitations
Reports djust from 0.9.0 below 1.0.10, from 1.1.0 below 1.1.7 and from 1.2.0 below 1.2.4 where a version is stated: a requirements*.txt entry at any depth, a pyproject.toml, Pipfile or lockfile entry at the project root, or a uvx launch in .mcp.json, mcp.json or claude_desktop_config.json, reporting a range that admits an affected version. latest was 1.3.2 on 2026-11-11 and states no version, so an unversioned djust is not reported. A pre-release reads as its release: 1.3.0rc4 to 1.3.0rc7, which are affected, read as 1.3.0, which is fixed, and are not reported, while 1.2.1rc1 and 1.2.1rc2 read as 1.2.1 and are. It reads the version, not whether the project runs djust_mcp, so a site that never starts the MCP server is reported too. A file over 2 MB, or a lockfile over 32 MiB, is not read. A declaration nested more than 64 levels deep in package.json, a TOML manifest or an MCP config (an MCP server more than 62) is still judged, and reported without a line; a lockfile entry keeps its line at any depth.
References
- CVE: CVE-2026-113731
- OWASP MCP Top 10: MCP04:2025 (Software Supply Chain Attacks & Dependency Tampering), MCP05:2025 (Command Injection & Execution)
- OWASP Agentic Top 10: ASI02 (Tool Misuse and Exploitation), ASI04 (Agentic Supply Chain Vulnerabilities)
- Adversa AI MCP Top 25 (AAK-defined ids): ADV-INJECT-06 (Tool Param Path Traversal)
- CSA AI Controls Matrix (AICM): AIS-07, STA-08
All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-MCP-DJUST-CVE-2026-113731-001.md: the page then shows that text, with the registry reference appended under it.