djust: Six template-layer defects emit attacker-controlled markup unescaped (XSS)

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Five independent defects in djust's template auto-escaping cause attacker-controlled input to be rendered as live markup where Django escapes it. All four are present in shipped 1.1.0 and are fixed in 1.1.1. They share one shape: a filter or grant that escapes nothing itself and relies on the render-time auto-escape, which something downstream then removes. They are grouped into a single advisory because the mitigation is identical — upgrade to 1.1.1 — and because no single one of them is meaningfully actionable in isolation. 1. linenumbers never escaped its input (#2291) The filter deferred all escaping to render time; a trailing |safe suppressed exactly that. The exposure is wider than the |safe form: any downstream filter that reads the output as markup is affected, including {{ p|linenumbers|truncatecharshtml:"5" }}, which contains no |safe at all. 2. escape was a no-op (#2281) Django's escape is eager (conditionalescape, returning SafeString). djust's returned its input…

Published by the source

17 Sep 2026, 20:31 UTC

Last modified by the source

17 Sep 2026, 20:45 UTC

Source last checked

26 Oct 2026, 13:52 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-9395-2g46-rj3f

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-9395-2g46-rj3f

3. Revision 1 · created · 23 Oct 2026

   Published from ghsa record GHSA-9395-2g46-rj3f

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-9395-2g46-rj3f

Advisory: djust: Six template-layer defects emit attacker-controlled markup unescaped (XSS)
IDs: GHSA-9395-2g46-rj3f
Record: https://patchnext.com/advisories/ghsa-9395-2g46-rj3f (revision 3, 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: Unrated
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.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI djust: affected <= 1.1.0; fixed in 1.1.1

## 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-9395-2g46-rj3f (GitHub-reviewed advisory GHSA-9395-2g46-rj3f lists affected ranges: PyPI djust >=0 <=1.1.0)
- Verified: https://osv.dev/vulnerability/GHSA-9395-2g46-rj3f (OSV record GHSA-9395-2g46-rj3f lists affected ranges: PyPI djust >=0 <1.1.1 (fixed))

Commands are suggestions: review each one before running it.