CVE-2021-28363Not scoredCWE-295

CVE-2021-28363: Python Urllib3 vulnerability

Python · Urllib3

Fixed in 1.26.4 · Affected: Python Urllib3 before 1.26.4 · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

2.2%probability of exploitation in the next 30 days

82nd percentile

050100

Higher than 82% of scored CVEs

Not scored yet. The CVE record carries no CVSS score.

DescriptionCVE.org

The urllib3 library 1.26.x before 1.26.4 for Python omits SSL certificate validation in some cases involving HTTPS to HTTPS proxies. The initial connection to the HTTPS proxy (if an SSLContext isn't given via proxy_config) doesn't verify the hostname of the certificate. This means certificates for different servers that still validate properly with the default urllib3 SSLContext will be silently accepted.

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Improper Certificate Validation · Cryptography
Vendor: Python
Published: March 2021
Band: Possible (1 to 10%), March 2021

CoverageNo articles yet

No CyberSIXT article names CVE-2021-28363 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.