What’s Vulnerable › Vulnerabilities

CVE-2020-35681

• Severity: high (CVSS 7.4 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 2.7% probability of exploitation in the next 30 days
• Public exploit or detection template: yes
• Published: 2021-02-22 · updated 2026-06-17
• Weakness: CWE-200

Description

Django Channels 3.x before 3.0.3 allows remote attackers to obtain sensitive information from a different request scope. The legacy channels.http.AsgiHandler class, used for handling HTTP type requests in an ASGI environment prior to Django 3.0, did not correctly separate request scopes in Channels 3.0. In many cases this would result in a crash but, with correct timing, responses could be sent to the wrong client, resulting in potential leakage of session identifiers and other sensitive data. Note that this affects only the legacy Channels provided class, and not Django's similar ASGIHandler, available from Django 3.0.

Affected products

• djangoproject Channels: from 3.0.0 before 3.0.3 — fixed in 3.0.3

How to fix

Upgrade to a fixed version: djangoproject Channels 3.0.3. Check the vendor advisory for mitigations.

References

• https://channels.readthedocs.io/en/stable/releases/3.0.3.html
• https://channels.readthedocs.io/en/stable/releases/index.html
• https://github.com/django/channels/releases
• https://channels.readthedocs.io/en/stable/releases/3.0.3.html
• https://channels.readthedocs.io/en/stable/releases/index.html
• https://github.com/django/channels/releases

Get alerted when CVE-2020-35681 or the next vulnerability affects your stack