USN-8344-2
Vulnerability from osv_ubuntu – Published: 2026-05-29 19:53 – Updated: 2026-05-29 19:53 – Source websiteUSN-8344-1 fixed vulnerabilities in pip. On Ubuntu 22.04 LTS, Ubuntu 24.04 LTS, and Ubuntu 26.04 LTS the patches for CVE-2025-66471 caused a regression when using pip. The patches for CVE-2025-66471 have been temporarily reverted pending investigation.
We apologize for the inconvenience.
Original advisory details:
It was discovered that pip incorrectly handled TLS certificate verification in session connections. If a session was first used with certificate verification disabled, subsequent requests to the same host would also skip verification regardless of the session's current settings. A remote attacker could possibly use this issue to perform a machine-in-the-middle attack and expose sensitive information. (CVE-2024-35195)
It was discovered that pip's bundled urllib3 library did not limit the number of decompression steps when processing HTTP responses. A remote attacker could possibly use this issue to cause pip to consume excessive resources, leading to a denial of service. (CVE-2025-66418)
It was discovered that pip's bundled urllib3 library improperly handled streaming decompression of highly compressed data. A remote attacker could possibly use this issue to cause pip to consume excessive resources, leading to a denial of service. (CVE-2025-66471)
| URL | Type | |
|---|---|---|
{
"affected": [
{
"database_specific": {
"cves_map": {
"cves": [],
"ecosystem": "Ubuntu:Pro:22.04:LTS"
}
},
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "python3-pip",
"binary_version": "22.0.2+dfsg-1ubuntu0.7+esm2"
},
{
"binary_name": "python3-pip-whl",
"binary_version": "22.0.2+dfsg-1ubuntu0.7+esm2"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:22.04:LTS",
"name": "python-pip",
"purl": "pkg:deb/ubuntu/python-pip@22.0.2+dfsg-1ubuntu0.7+esm2?arch=source\u0026distro=esm-apps/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "22.0.2+dfsg-1ubuntu0.7+esm2"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"20.3.4-4",
"21.3.1+dfsg-3",
"22.0.2+dfsg-1",
"22.0.2+dfsg-1ubuntu0.1",
"22.0.2+dfsg-1ubuntu0.2",
"22.0.2+dfsg-1ubuntu0.3",
"22.0.2+dfsg-1ubuntu0.4",
"22.0.2+dfsg-1ubuntu0.5",
"22.0.2+dfsg-1ubuntu0.6",
"22.0.2+dfsg-1ubuntu0.7",
"22.0.2+dfsg-1ubuntu0.7+esm1"
]
},
{
"database_specific": {
"cves_map": {
"cves": [],
"ecosystem": "Ubuntu:Pro:24.04:LTS"
}
},
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "python3-pip",
"binary_version": "24.0+dfsg-1ubuntu1.3+esm2"
},
{
"binary_name": "python3-pip-whl",
"binary_version": "24.0+dfsg-1ubuntu1.3+esm2"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:24.04:LTS",
"name": "python-pip",
"purl": "pkg:deb/ubuntu/python-pip@24.0+dfsg-1ubuntu1.3+esm2?arch=source\u0026distro=esm-apps/noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "24.0+dfsg-1ubuntu1.3+esm2"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"23.2+dfsg-1",
"23.3+dfsg-1",
"24.0+dfsg-1",
"24.0+dfsg-1ubuntu1",
"24.0+dfsg-1ubuntu1.1",
"24.0+dfsg-1ubuntu1.2",
"24.0+dfsg-1ubuntu1.3",
"24.0+dfsg-1ubuntu1.3+esm1"
]
},
{
"database_specific": {
"cves_map": {
"cves": [],
"ecosystem": "Ubuntu:Pro:26.04:LTS"
}
},
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "python3-pip",
"binary_version": "25.1.1+dfsg-1ubuntu2+esm2"
},
{
"binary_name": "python3-pip-whl",
"binary_version": "25.1.1+dfsg-1ubuntu2+esm2"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:26.04:LTS",
"name": "python-pip",
"purl": "pkg:deb/ubuntu/python-pip@25.1.1+dfsg-1ubuntu2+esm2?arch=source\u0026distro=esm-apps/resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "25.1.1+dfsg-1ubuntu2+esm2"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"25.1.1+dfsg-1ubuntu2",
"25.1.1+dfsg-1ubuntu2+esm1"
]
}
],
"aliases": [],
"details": "USN-8344-1 fixed vulnerabilities in pip. On Ubuntu 22.04 LTS, Ubuntu 24.04 LTS,\nand Ubuntu 26.04 LTS the patches for CVE-2025-66471 caused a regression when\nusing pip. The patches for CVE-2025-66471 have been temporarily reverted\npending investigation.\n\nWe apologize for the inconvenience.\n\nOriginal advisory details:\n\n It was discovered that pip incorrectly handled TLS certificate\n verification in session connections. If a session was first used with\n certificate verification disabled, subsequent requests to the same host\n would also skip verification regardless of the session\u0027s current settings.\n A remote attacker could possibly use this issue to perform a machine-in-the-middle\n attack and expose sensitive information. (CVE-2024-35195)\n\n It was discovered that pip\u0027s bundled urllib3 library did not limit the\n number of decompression steps when processing HTTP responses. A remote\n attacker could possibly use this issue to cause pip to consume excessive resources,\n leading to a denial of service. (CVE-2025-66418)\n\n It was discovered that pip\u0027s bundled urllib3 library improperly\n handled streaming decompression of highly compressed data. A remote\n attacker could possibly use this issue to cause pip to consume excessive resources,\n leading to a denial of service. (CVE-2025-66471)",
"id": "USN-8344-2",
"modified": "2026-05-29T19:53:25Z",
"published": "2026-05-29T19:53:25Z",
"references": [
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-8344-2"
},
{
"type": "REPORT",
"url": "https://launchpad.net/bugs/2154576"
}
],
"related": [],
"schema_version": "1.7.0",
"summary": "python-pip regression",
"upstream": []
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.