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.
References
| Link | Resource |
|---|---|
| https://github.com/django-commons/django-unicorn/security/advisories/GHSA-ffv6-jj46-x367 | Exploit Vendor Advisory |
Configurations
History
18 Mar 2026, 19:36
| Type | Values Removed | Values Added |
|---|---|---|
| CPE | cpe:2.3:a:django-unicorn:unicorn:*:*:*:*:*:django:*:* | |
| First Time |
Django-unicorn unicorn
Django-unicorn |
|
| References | () https://github.com/django-commons/django-unicorn/security/advisories/GHSA-ffv6-jj46-x367 - Exploit, Vendor Advisory |
11 Mar 2026, 13:52
| Type | Values Removed | Values Added |
|---|---|---|
| Summary |
|
10 Mar 2026, 22:16
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-03-10 22:16
Updated : 2026-03-18 19:36
NVD link : CVE-2026-31815
Mitre link : CVE-2026-31815
CVE.ORG link : CVE-2026-31815
JSON object : View
Products Affected
django-unicorn
- unicorn
