All reports
Medium

Using default SSLContext for HTTPS requests in an HTTPS proxy doesn't verify certificate hostname for proxy connection

Affected versions

Version ranges need review.

Affected versions
>=1.26.0 <1.26.4
Fixed version
1.26.4
Affected versions
>= 1.26.0, < 1.26.4
Fixed version
1.26.4
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2021-28363

Probability of exploitation in the next 30 days: 2.17%

FIRST EPSS · 2026-11-19

Description

Impact

Users who are using an HTTPS proxy to issue HTTPS requests and haven't configured their own SSLContext via proxy_config. Only the default SSLContext is impacted.

Patches

urllib3 >=1.26.4 has the issue resolved. urllib3<1.26 is not impacted due to not supporting HTTPS requests via HTTPS proxies.

Workarounds

Upgrading is recommended as this is a minor release and not likely to break current usage.

Configuring an SSLContext with check_hostname=True and passing via proxy_config instead of relying on the default SSLContext

For more information

If you have any questions or comments about this advisory:

  • Email us at sethmichaellarson@gmail.com

Links

Credits

  • jalopezsilva
  • pquentin