CYBERSECURITYTRACKER
Permanent story citation

Django CVE-2026-108147, CVE-2026-111211, CVE-2026-111362, CVE-2026-113593, CVE-2026-113733, and CVE-2026-114582

This page keeps the story as Cybersecurity Tracker first published it. If the tracker later corrects it, the correction appears below the original and never replaces it.

Back to newsStory 12255

As cited

Copy frozen at (site build).

vulnerabilities

Django CVE-2026-108147, CVE-2026-111211, CVE-2026-111362, CVE-2026-113593, CVE-2026-113733, and CVE-2026-114582

Django released security updates on November 3, 2026, addressing six vulnerabilities identified as CVE-2026-108147, CVE-2026-111211, CVE-2026-111362, CVE-2026-113593, CVE-2026-113733, and CVE-2026-114582. Details about the specific impacts and affected versions were provided in the official announcement and corresponding CVE records.

Why it matters: Django users need to review the official security advisory to determine which versions require updates and plan patching based on their deployment versions.

Source published
First seen by Cybersecurity Tracker

Source attribution

Correction

Correction recorded as of .

vulnerabilities

Django CVE-2026-108147, CVE-2026-111211, CVE-2026-111362, CVE-2026-113593, CVE-2026-113733, and CVE-2026-114582

Django released security patches for six vulnerabilities on November 3, 2026. The announcement and CVE records are available through the Django project website and the CVE database.

Why it matters: Django developers and operators must apply these patches to systems running affected Django versions to address the disclosed vulnerabilities.

Source published
First seen by Cybersecurity Tracker

Source attribution

Glossary