Unicorn adds modern reactive component functionality to your Django templates. Prior to 0.67.0, component state manipulation is possible in django-unicorn due to missing access control checks during property updates and method calls. An attacker can bypass the intended _is_public protection to modify internal attributes such as template_name or trigger protected methods. This vulnerability is fixed in 0.67.0.
CVE-2026-31815
This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(low)
- EG Risk
- 28(Track)EG Risk 28/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity53% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 11%
- KEV
- Not listed
Published
March 10, 2026
Last Modified
June 17, 2026
References (1)
- security-advisories@githubhttps://github.com/django-commons/django-unicorn/security/advisories/GHSA-ffv6-jj46-x367
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| django-unicorn | 0.1.0 ... 0.9.4 (112 versions) | 0.67.0 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-28 15:36 UTCEPSS rescore
- 2026-07-27 13:44 UTCEG score recompute
Frequently asked(5)
What is CVE-2026-31815?
When was CVE-2026-31815 disclosed?
Is CVE-2026-31815 actively exploited?
What is the CVSS score of CVE-2026-31815?
How do I remediate CVE-2026-31815?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-31815
Is Your Infrastructure Affected by CVE-2026-31815?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.