CVE-2026-31815
Received Received - Intake
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
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-10
Last Modified
2026-03-18
Generated
2026-06-16
AI Q&A
2026-03-11
EPSS Evaluated
2026-06-15
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
django-unicorn unicorn to 0.67.0 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
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.
CWE-284 The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

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.

Impact Analysis

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.

Compliance Impact

I don't know

Detection Guidance

I don't know

Mitigation Strategies

To mitigate this vulnerability, you should upgrade django-unicorn to version 0.67.0 or later, where the issue has been fixed.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-31815. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart