djust: Arbitrary absolute-path file read in the find_handlers_for_template MCP tool

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

3.3 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2026-113731: 0.19% estimated exploitation activity in the next 30 days; percentile 8.36 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Affected version / file / line Version: djust v1.1.4 (latest release, published 2026-09-23). File: python/djust/mcp/server.py:354-433 (MCP tool findhandlersfortemplate). Confirmed identical on the commit used for triage, a7e4fafd1667b4db0b1465652d4a63cb17117a07. Description When templatepath is an absolute path to an existing file, it is used directly, with no confinement to the project/template directories — no realpath() + prefix check, no allowlist. open(resolvedpath, ...) then reads the file. This is inconsistent with the sibling tool in the same file (loaddata, ~line 290-303), which explicitly rejects paths outside the project directory for its own path-like parameter: findhandlersfortemplate has no equivalent check for templatepath before the open() call. Impact An MCP client with access to this tool (available whenever the Django project is running the MCP server via python manage.py djustmcp — no separate opt-in flag gates this specific tool beyond that) can read the contents…

Published by the source

21 Oct 2026, 17:21 UTC

Last modified by the source

21 Oct 2026, 17:21 UTC

Source last checked

26 Oct 2026, 13:55 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-r57g-mc79-8hj2

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-113731

Advisory: djust: Arbitrary absolute-path file read in the find_handlers_for_template MCP tool
IDs: CVE-2026-113731, GHSA-r57g-mc79-8hj2
Record: https://patchnext.com/advisories/cve-2026-113731 (revision 1, source checked 26 Oct 2026, 13:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: djust 1.3.0rc8, 1.2.4, 1.1.7, 1.0.10. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI djust: affected >= 0.9.0, <= 1.0.9; >= 1.1.0, <= 1.1.6; >= 1.2.0.dev0, <= 1.2.3; >= 1.3.0.dev0, <= 1.3.0rc7; fixed in 1.0.10, 1.1.7, 1.2.4, 1.3.0rc8

## Suggested inspection (read-only)
- `python -m pip show djust`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on djust.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-r57g-mc79-8hj2 (GitHub-reviewed advisory GHSA-r57g-mc79-8hj2 lists affected ranges: PyPI djust >=0.9.0 =1.1.0 =1.2.0.dev0 =1.3.0.dev0 <=1.3.0rc7)

Commands are suggestions: review each one before running it.