Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.3amended

Django-Unicorn Class Pollution Vulnerability, Leading to XSS, DoS and Authentication Bypass

CVE-2025-24370GHSA-g9wf-5777-gq43

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (django-unicorn 0.62.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.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
9.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2025-24370: 0.49% estimated exploitation activity in the next 30 days; percentile 42.33 (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 Django-Unicorn is vulnerable to python class pollution vulnerability, a new type of vulnerability categorized under CWE-915. The vulnerability arises from the core functionality `set_property_value`, which can be remotely triggered by users by crafting appropriate component requests and feeding in values of second and third parameter to the vulnerable function, leading to arbitrary changes to the python runtime status. At least five ways of vulnerability exploitation have been found, stably resulting in Cross-Site Scripting (XSS), Denial of Service (DoS), and Authentication Bypass attacks in almost every Django-Unicorn-based application.

Analysis of Vulnerable Function By taking a look at the vulnerable function `set_property_value` located at: `django_unicorn/views/action_parsers/utils.py`. You can observe the functionality is responsible for modifying a property value of an object. The property is specified by a dotted…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 5 · amended ·

    Amended from osv record GHSA-g9wf-5777-gq43

  2. Revision 4 · amended ·

    Amended from ghsa record GHSA-g9wf-5777-gq43

  3. Revision 3 · amended ·

    Amended from ghsa record GHSA-g9wf-5777-gq43

  4. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  5. Revision 1 · created ·

    Published from osv record GHSA-g9wf-5777-gq43

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-2025-24370

Advisory: Django-Unicorn Class Pollution Vulnerability, Leading to XSS, DoS and Authentication Bypass
IDs: CVE-2025-24370, GHSA-g9wf-5777-gq43
Record: https://patchnext.com/advisories/cve-2025-24370 (revision 5, source checked 28 Oct 2026, 06:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.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.62.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI django-unicorn: affected < 0.62.0; fixed in 0.62.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-g9wf-5777-gq43 (OSV record GHSA-g9wf-5777-gq43 lists affected ranges: PyPI django-unicorn >=0 <0.62.0 (fixed))
- Verified: https://github.com/advisories/GHSA-g9wf-5777-gq43 (GitHub-reviewed advisory GHSA-g9wf-5777-gq43 lists affected ranges: PyPI django-unicorn >=0 <0.62.0)

Commands are suggestions: review each one before running it.

Loading voting…