Advisory record · GHSA-g9wf-5777-gq43

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

CVSS 9.3 CriticalCriticalEPSS 0.0051 · 44th percentile

Critical, because:

  • CVSS score 9.3: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 3 Feb 2025, 15:48 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
django-unicornPyPI<0.62.00.62.0
Identifiers
GHSA-g9wf-5777-gq43 · CVE-2025-24370 · PYSEC-2026-329
Weakness (CWE)
CWE-915
Published
3 Feb 2025
Updated
27 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Django-Unicorn versions before 0.62.0 are vulnerable to Python class pollution through the set_property_value function, which can be reached remotely by crafting component requests with dotted property paths and values. An attacker who can send such requests can use magic attributes to reach global objects in the component's module and its dependencies, which the source says enables reflected and stored cross-site scripting, denial of service, and authentication bypass through overwriting the secret key. The fixed version is 0.62.0, so upgrade to that release or later.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.3 Critical 4.0 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 CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0051, the 44th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:07 UTC First seen by agentprime
  2. 31 Oct 2026, 14:07 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.