Vulnerability in django-unicorn (CVE-2026-31815)
Summary
Vulnerability in django-unicorn (CVE-2026-31815). Risk of unauthorized operations or information disclosure. Exploitable via _is_public. Mitigation: upgrade to 0.67.0 or later.
Original description
The description as published by the source.
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.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-31815 has been found in django-unicorn.
Attackers can target a specific entry point like _is_public over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade django-unicorn to 0.67.0 or later.
If unsure, ask your IT team or search "django-unicorn CVE-2026-31815" on the vendor's site.
CVE-2026-31815 (django-unicorn) — CWE-284
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: _is_public / template_name / getattr / setattr
Patched: 0.67.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-284) exists in django-unicorn. Attackers reach the vulnerable code path via _is_public without authentication.
Check the vendor advisory for the affected versions of django-unicorn. Attack surface: _is_public / template_name / getattr / setattr.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.67.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'django-unicorn' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'django-unicorn' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
django-unicornを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade django-unicorn to 0.67.0ステージング環境で 0.67.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com