CVE-2026-113731 — djust: Arbitrary absolute-path file read in the find_handlers_for_template MCP tool
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Djust-org Djust).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (file handling), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 3.3 | CVSS 3.1 | Low | 1.8 | 1.4 | security-advisories@github.com via NIST National Vulnerability Database |
| 3.3 | CVSS 3.1 | Low | — | — | GitHub_M via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N (score shown at the top: security-advisories@github.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 21, 2026 → Oct 25, 2026 · 5 reading(s) · max 0.19%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
- Monitor file creation in web directories and paths with traversal sequences (../).
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · djust-org/djust
- Record published
- CVSS changed · 3.3
- Source status changed · → Deferred
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 20, 2026 – Oct 20, 2026
References
9 on the record
- github.com/djust-org/djust/releases/tag/v1.1.7
- github.com/djust-org/djust/commit/45a5045793ebe7c9c2df86b0ad34275af6822619
- github.com/djust-org/djust/commit/a62caf6b4ef540ad688d4dfdfa407ff914c78728
- github.com/djust-org/djust/commit/85eed7caaf620bdb08986f2f3bb79432c0d3d715
- github.com/djust-org/djust/commit/744bccf699c65c815d9379b36236a7c5592a339b
- github.com/djust-org/djust/security/advisories/GHSA-r57g-mc79-8hj2
- github.com/djust-org/djust/releases/tag/v1.0.10
- github.com/djust-org/djust/releases/tag/v1.2.4
- github.com/djust-org/djust/releases/tag/v1.3.0rc8
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-61599 djust has an unauthenticated arbitrary module import via the WebSocket/SSE view-mount path Sep 16, 2026
- Medium CVE-2026-61589 djust: WebSocket/runtime reconstructed request omits the client Host, causing host/subdomain TenantResolvers to misresolve the tenant on the live path Sep 16, 2026
- High CVE-2026-61596 djust has broken object-level access control (IDOR) Sep 16, 2026
- Medium CVE-2026-61588 djust's Django model serialization has no sensitive-field denylist: password hashes, privilege flags, and PII on a public view attribute are sent to the client Sep 16, 2026
- Critical CVE-2026-61594 djust has an authorization bypass on the WebSocket/SSE mount path Sep 16, 2026
- Medium CVE-2026-61597 djust is vulnerable to stored/reflected XSS via javascript: URLs in built-in component template tags Sep 16, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-113731 is "djust: Arbitrary absolute-path file read in the find_handlers_for_template MCP tool", rated Low. It affects Djust (Djust-org); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 3.3 describes technical severity. EPSS 0.19% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.