# CVE-2026-113731: djust: Arbitrary absolute-path file read in the find_handlers_for_template MCP tool


- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 20 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-r57g-mc79-8hj2

## What is CVE-2026-113731?

CVE-2026-113731 is a low-severity vulnerability in djust-org djust, published on 20 Oct 2026. 

### Official description

djust provides Phoenix LiveView-style reactive server-side rendering for Django with Rust-powered performance. From 0.9.0 until 1.0.10, 1.1.7, 1.2.4, and 1.3.0rc8, the find_handlers_for_template MCP tool in python/djust/mcp/server.py accepts an existing absolute template_path and reads it without restricting the resolved path to the project or configured template directories. A local MCP client can use the tool as a file existence and readability oracle and can obtain substrings that match the tool's dj-click, dj-submit, dj-change, dj-input, dj-keydown, or dj-keyup attribute pattern from files readable by the djust process. The maintainer assessment states that the MCP server communicates over local stdio as the same operating-system user and has no network listener, and the tool does not return arbitrary raw file contents. This issue is fixed in versions 1.0.10, 1.1.7, 1.2.4, and 1.3.0rc8.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-113731?

8 open source packages ship an affected version, including djust.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `djust` | PyPI | From 0.9.0 | 1.0.10 |
| `djust` | PyPI | From 0.9.0 | 1.0.10 |
| `djust` | PyPI | From 1.1.0 | 1.1.7 |
| `djust` | PyPI | From 1.1.0 | 1.1.7 |
| `djust` | PyPI | From 1.2.0.dev0 | 1.2.4 |
| `djust` | PyPI | From 1.2.0.dev0 | 1.2.4 |
| `djust` | PyPI | From 1.3.0.dev0 | 1.3.0rc8 |
| `djust` | PyPI | From 1.3.0.dev0 | 1.3.0rc8 |

## How do I fix CVE-2026-113731?

Upgrade djust to a fixed version for your release line: 1.0.10, 1.1.7, 1.2.4 or 1.3.0rc8.

## Is CVE-2026-113731 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-113731 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-113731 and fix it if it is affected.

What it is: CVE-2026-113731 is a low-severity vulnerability in djust-org djust, published on 20 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-113731 exists.

Affected packages and fixed versions:
- djust (PyPI): affected from 0.9.0; fixed in 1.0.10
- djust (PyPI): affected from 0.9.0; fixed in 1.0.10
- djust (PyPI): affected from 1.1.0; fixed in 1.1.7
- djust (PyPI): affected from 1.1.0; fixed in 1.1.7
- djust (PyPI): affected from 1.2.0.dev0; fixed in 1.2.4
- djust (PyPI): affected from 1.2.0.dev0; fixed in 1.2.4
- djust (PyPI): affected from 1.3.0.dev0; fixed in 1.3.0rc8
- djust (PyPI): affected from 1.3.0.dev0; fixed in 1.3.0rc8

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-113731/ (Markdown: https://insights.sbomify.com/CVE-2026-113731/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-113731
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-113731
- OSV: https://osv.dev/vulnerability/CVE-2026-113731

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-113731/
Summaries are generated and may contain mistakes; the official description above is the record.