djust: A template binding inherits a context safety grant it never earned (XSS)
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (djust 1.1.2), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI djust
- Affected
- <= 1.1.1
- Fixed in
- 1.1.2
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-xjw9-38cr-6372 lists affected ranges: PyPI djust >=0 <=1.1.1
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-xjw9-38cr-6372 lists affected ranges: PyPI djust >=0 <1.1.2 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N · score source
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
A context safety grant was inherited by a template binding that never earned it, so rebinding a name the view had marked safe left the mark attached to the new, attacker-controlled value. djust's context safety channel is keyed by name, not by value. Every bind copied the value and left the grant in place: Affected binds Eight distinct shapes were live. All are fixed in 1.1.2: | shape | example | |---|---| | {% with %} rebinding a marked name | {% with p=hostile %}{{ p }}{% endwith %} | | {% with %} descendant of a rebound name | {% with p=hostile %}{{ p.a }}{% endwith %} | | {% with %} binding over a marked name | {% with q=hostile %}{{ q }}{% endwith %} | | {% for %} loop variable | {% for p in hostiles %}{{ p }}{% endfor %} | | {% for %} descendant | {% for p in hostiles %}{{ p.a }}{% endfor %} | | {% for %} tuple unpacking | {% for k, v in rows %}{{ v }}{% endfor %} | | {% include … with %} | {% include "c.html" with q=hostile %} | | assign tags | {% … as x %} | No filter chain…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 4 · amended ·
Amended from ghsa record GHSA-xjw9-38cr-6372
- Revision 3 · amended ·
Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.
- Revision 2 · amended ·
Amended from osv record GHSA-xjw9-38cr-6372
- Revision 1 · created ·
Published from ghsa record GHSA-xjw9-38cr-6372
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-xjw9-38cr-6372 Advisory: djust: A template binding inherits a context safety grant it never earned (XSS) IDs: GHSA-xjw9-38cr-6372 Record: https://patchnext.com/advisories/ghsa-xjw9-38cr-6372 (revision 4, source checked 26 Oct 2026, 13:52 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 8.7) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: djust 1.1.2. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI djust: affected <= 1.1.1; fixed in 1.1.2 ## 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-xjw9-38cr-6372 (GitHub-reviewed advisory GHSA-xjw9-38cr-6372 lists affected ranges: PyPI djust >=0 <=1.1.1) - Verified: https://osv.dev/vulnerability/GHSA-xjw9-38cr-6372 (OSV record GHSA-xjw9-38cr-6372 lists affected ranges: PyPI djust >=0 <1.1.2 (fixed)) Commands are suggestions: review each one before running it.
Loading voting…