<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Vulnerability Spoiler Alert - django/django</title>
    <link>https://spaceraccoon.github.io/vulnerability-spoiler-alert</link>
    <description>Vulnerability alerts for django/django</description>
    <language>en-us</language>
    <lastBuildDate>Fri, 17 Apr 2026 01:52:35 GMT</lastBuildDate>
    <atom:link href="https://spaceraccoon.github.io/vulnerability-spoiler-alert/feed/django-django.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>[MEDIUM] Denial of Service (DoS) in django/django</title>
      <link>https://github.com/spaceraccoon/vulnerability-spoiler-alert/issues/66</link>
      <guid isPermaLink="true">https://github.com/spaceraccoon/vulnerability-spoiler-alert/issues/66</guid>
      <pubDate>Tue, 03 Mar 2026 14:31:49 GMT</pubDate>
      <description>Django&apos;s URLField.to_python() used urlsplit() to detect URL schemes, which on Windows performs NFKC Unicode normalization. This normalization is disproportionately slow for inputs containing certain Unicode characters (e.g., characters like &apos;¾&apos;), allowing an attacker to craft a POST payload that causes excessive CPU consumption. The patch replaces urlsplit() with str.partition(&apos;:&apos;) for scheme detection, avoiding Unicode normalization entirely.</description>
      <category>medium</category>
      <category>unverified</category>
    </item>
    <item>
      <title>[LOW] Incorrect Permissions / Race Condition (umask) in django/django</title>
      <link>https://github.com/spaceraccoon/vulnerability-spoiler-alert/issues/65</link>
      <guid isPermaLink="true">https://github.com/spaceraccoon/vulnerability-spoiler-alert/issues/65</guid>
      <pubDate>Tue, 03 Mar 2026 14:31:34 GMT</pubDate>
      <description>In multi-threaded Django applications, the file-based cache backend and filesystem storage used temporary umask changes (via os.umask()) to control directory permissions when creating directories. Because os.umask() is a process-wide operation, a temporary umask change in one thread could affect directory/file creation in other threads, resulting in file system objects being created with unintended (potentially overly permissive) permissions. The patch replaces the umask manipulation approach with a safe_makedirs() function that uses os.chmod() after os.mkdir() to enforce the exact requested permissions.</description>
      <category>low</category>
      <category>unverified</category>
    </item>
    <item>
      <title>[MEDIUM] Cross-Site Scripting (XSS) in django/django</title>
      <link>https://github.com/spaceraccoon/vulnerability-spoiler-alert/issues/44</link>
      <guid isPermaLink="true">https://github.com/spaceraccoon/vulnerability-spoiler-alert/issues/44</guid>
      <pubDate>Fri, 20 Feb 2026 14:47:10 GMT</pubDate>
      <description>The Django admin interface was vulnerable to XSS attacks when displaying model string representations that contained only whitespace or malicious scripts. The vulnerability occurred because whitespace-only strings were not properly sanitized before being rendered in HTML contexts, allowing attackers to inject malicious scripts through model __str__ methods.</description>
      <category>medium</category>
      <category>unverified</category>
    </item>
  </channel>
</rss>