django-unicorn affected by component state manipulation via unvalidated attribute access
CVE-2026-31815GHSA-ffv6-jj46-x367
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (django-unicorn 0.67.0), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI django-unicorn
- Affected
- < 0.67.0
- Fixed in
- 0.67.0
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-ffv6-jj46-x367 lists affected ranges: PyPI django-unicorn >=0 <0.67.0 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-ffv6-jj46-x367 lists affected ranges: PyPI django-unicorn >=0 <0.67.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- EPSS
- CVE-2026-31815: 0.22% estimated exploitation activity in the next 30 days; percentile 12.97 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary 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 ispublic protection to modify internal attributes such as templatename or trigger protected methods. Vulnerability Details: Component Access Control Bypass Security analysis identified that the framework fails to enforce visibility boundaries defined by ispublic within the action parsers. Specifically, the logic in setpropertyvalue() and callmethodname() utilizes getattr and setattr directly on component instances without verifying if the target attribute or method is explicitly marked as public. Vulnerability resides in: - src/djangounicorn/views/actionparsers/callmethod.py - src/djangounicorn/views/actionparsers/utils.py While Django's template engine restricts rendering to registered directories, an unauthorized user can still force a component to render sensitive templates (e.g., admin layouts) from…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-ffv6-jj46-x367
- Revision 1 · created ·
Published from osv record GHSA-ffv6-jj46-x367
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-31815 Advisory: django-unicorn affected by component state manipulation via unvalidated attribute access IDs: CVE-2026-31815, GHSA-ffv6-jj46-x367 Record: https://patchnext.com/advisories/cve-2026-31815 (revision 2, source checked 26 Oct 2026, 13:37 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.3) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: django-unicorn 0.67.0. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI django-unicorn: affected < 0.67.0; fixed in 0.67.0 ## Suggested inspection (read-only) - `python -m pip show django-unicorn`: prints the installed version. Run with the environment that serves production active. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on django-unicorn. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-ffv6-jj46-x367 (OSV record GHSA-ffv6-jj46-x367 lists affected ranges: PyPI django-unicorn >=0 <0.67.0 (fixed)) - Verified: https://github.com/advisories/GHSA-ffv6-jj46-x367 (GitHub-reviewed advisory GHSA-ffv6-jj46-x367 lists affected ranges: PyPI django-unicorn >=0 <0.67.0) Commands are suggestions: review each one before running it.
Loading voting…