Vulnerability in Django-Commons Django-Unicorn
CVE-2026-31815
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.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 5.3 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N.
EPSS exploit prediction
EPSS: 0.003 (21.1th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 21st percentile — 21.1% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.002 · newest: 0.003 · change: +0.001
Affected products
- Django-Commons Django-Unicorn — versions < 0.67.0
- Django-Unicorn Unicorn
Weakness classification (CWE)
References
- github.com/django-commons/django-unicorn/security/advisories/GHSA-ffv6-jj46-x367 (Exploit, Vendor Advisory)
Frequently asked questions
- What is CVE-2026-31815?
- CVE-2026-31815 is a medium-severity vulnerability in Django-Commons Django-Unicorn, classified under Improper Access Control. CVSS score: 5.3/10. Published 2026-03-10.
- How severe is CVE-2026-31815?
- Medium severity. CVSS v3 base score is 5.3 out of 10.