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


- **Severity:** Low 2.3 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 9 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-xjw9-38cr-6372

## What is CVE-2026-125112?

CVE-2026-125112 is a low-severity vulnerability in djust-org djust, published on 9 Nov 2026. 

### Official 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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-116 (Improper Encoding or Escaping of Output)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `djust` | PyPI | All versions | 1.0.10 |
| `djust` | PyPI | From 1.1.0 | 1.1.2 |

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

Upgrade djust to a fixed version for your release line: 1.0.10 or 1.1.2.

## Is CVE-2026-125112 being exploited?

There is no known exploitation of CVE-2026-125112 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-125112 is a low-severity vulnerability in djust-org djust, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-125112 in the wild and no public exploit code.

Affected packages and fixed versions:
- djust (PyPI): affected all versions; fixed in 1.0.10
- djust (PyPI): affected from 1.1.0; fixed in 1.1.2

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-125112/ (Markdown: https://insights.sbomify.com/CVE-2026-125112/index.md)
```

## Sources

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

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