CVE-2026-31815: Unicorn adds modern reactive component functionality to your Django templates

Q: How do I fix CVE-2026-31815?

unicorn: upgrade to 0.67.0. Exact commands for each OS are on this page.

Q: Is CVE-2026-31815 being exploited?

CVE-2026-31815 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-31815 affect?

CVE-2026-31815 affects unicorn. Severity is medium (CVSS 5.3). 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 att

Q: How urgent is CVE-2026-31815?

Priority 32/100. Public exploit reference; Remotely exploitable, no login, no user action

This week

MEDIUM 5.3REMOTEUPGRADE

CVE-2026-31815 is a medium-severity flaw (CVSS 5.3) affecting unicorn. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.2% (top 87%)
CISA exploited list	No
Weakness	CWE-284, CWE-915
Published	2026-03-10
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: django-unicorn

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-03-10 22:16 UTCPublished CVE record published
2026-06-17 10:34 UTCUpdated Record last modified

django-unicorn unicorn UPGRADE

Affected: < 0.67.0

Fixed in: 0.67.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy unicorn || rpm -q unicorn || unicorn --version

2. UPGRADE to 0.67.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade unicorn

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade unicorn

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-31815?

unicorn: upgrade to 0.67.0. Exact commands for each OS are on this page.

Is CVE-2026-31815 being exploited?

CVE-2026-31815 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-31815 affect?

CVE-2026-31815 affects unicorn. Severity is medium (CVSS 5.3). 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 att

How urgent is CVE-2026-31815?

Priority 32/100. Public exploit reference; Remotely exploitable, no login, no user action

Software pages

Django vulnerabilities

References

← Back to latest CVEs