Skip to main content
CVE-2024-11168VulnerabilityPublished Updated

CVE-2024-11168: Python Software Foundation CPython · Server-Side Request Forgery

Affects Python Software Foundation CPythonSource CVE Database V5

0

Not known to be exploited · CVSS 6.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N/AU:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Nov 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
PyPIcpythonpkg:pypi/cpythonOther threatsAffected
  • =0
  • =3.10.0
  • =3.11.0
  • =3.12.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Upgrade CPython to a patched version once released by the Python Software Foundation that corrects the bracketed host validation logic in urllib.parse. 2. In the interim, implement strict input validation on URLs before processing, ensuring that bracketed hosts conform strictly to valid IPv6 or IPvFuture formats. 3. Employ network-level controls such as egress filtering and internal firewall rules to restrict server-initiated HTTP requests to trusted destinations only, limiting SSRF impact. 4. Use application-layer protections like web application firewalls (WAFs) configured to detect and block suspicious URL patterns or SSRF attempts. 5. Review and audit codebases for multiple URL parsing steps or components that may interpret URLs differently, standardizing on a single, secure parsing method. 6. Monitor logs for unusual outbound requests or anomalies in URL processing that could indicate exploitation attempts. 7. Educate developers about the risks of SSRF and the importance of proper URL validation and sanitization.

Description

The urllib.parse.urlsplit() and urlparse() functions improperly validated bracketed hosts (`[]`), allowing hosts that weren't IPv6 or IPvFuture. This behavior was not conformant to RFC 3986 and potentially enabled SSRF if a URL is processed by more than one URL parser.

References

Community reviews

Loading reviews…