CVE-2026-31815
Access Control Bypass in django-unicorn Enables Internal State Manipulation
Publication date: 2026-03-10
Last updated on: 2026-03-18
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| django-unicorn | unicorn | to 0.67.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-284 | The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. |
| CWE-915 | The product receives input from an upstream component that specifies multiple attributes, properties, or fields that are to be initialized or updated in an object, but it does not properly control which attributes can be modified. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in django-unicorn versions prior to 0.67.0, a tool that adds reactive component functionality to Django templates. Due to missing access control checks during property updates and method calls, an attacker can bypass the intended _is_public protection. This allows the attacker to manipulate internal attributes such as template_name or trigger protected methods, which should normally be restricted.
How can this vulnerability impact me? :
The vulnerability allows an attacker to modify internal component state and trigger protected methods without authorization. This can lead to unauthorized changes in the behavior or appearance of Django templates, potentially exposing sensitive information or causing unexpected application behavior. However, the CVSS score indicates a moderate impact primarily on confidentiality, with no direct impact on integrity or availability.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade django-unicorn to version 0.67.0 or later, where the issue has been fixed.