djust: A template binding inherits a context safety grant it never earned (XSS)
- Exploited
- No known exploitation
- Fix
- Fixed in 1.0.10, 1.1.2
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1.0.10, 1.1.2.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 9/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original 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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity2.3/10CVSS 2.3
- No patch0/5No signal
What would change the score
- Would score about 64 if added to CISA KEV
- Would score about 59 if CISA's SSVC rates exploitation active
- Would score about 24 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 1.0.10, 1.1.2.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- djust-org djust
fixed in 1.0.10; From 1.1.0 · fixed in 1.1.2
Evidence 6
- Advisory
- Repository
- Repository
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-125112
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: cve.now feed data
Which versions are affected by CVE-2026-125112?
djust: before 1.0.10; from 1.1.0 before 1.1.2.Source: cve.now feed data
How do I fix CVE-2026-125112?
Upgrade to a fixed version: 1.0.10, 1.1.2.Source: cve.now feed data