CVE-2021-3572

MEDIUMNVD 5.75.7—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.7 under NVD CVSS v3. EPSS exploit probability: 1.7%, top 25% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
5.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 2%CVSS: 5.7Exploit: Elevated riskExposed: 0

A fix is available — apply it.

A flaw was found in python-pip in the way it handled Unicode separators in git references. A remote attacker could possibly use this issue to install a different revision on a repository. The highest threat from this vulnerability is to data integrity. This is fixed in python-pip version 21.1.

CVSS v3
5.7
EG Score
5.7(medium)
EG Risk
46(Track)
EG Risk 46/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity57% × 45%
Exploitation40% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
2%
EPSS %ILE
77%
KEV
Not listed

Published

November 10, 2021

Last Modified

August 25, 2026

Advisory Details (2)

Auto-updated Aug 25, 2026
Patch available. Sources: redhat.
generic

NetApp Product Security

https://security.netapp.com/advisory/ntap-20240621-0006/
redhat Patch Available

1962856 – (CVE-2021-3572) CVE-2021-3572 python-pip: Incorrect handling of unicode separators in git references

Affected: Red Hat Enterprise Linux 7

https://bugzilla.redhat.com/show_bug.cgi?id=1962856

Vendor Advisories for CVE-2021-3572(4)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython3-pip (1.5.4-1ubuntu4+esm1) @ trusty2026-08-25ubuntu
redhatpython39-devel:3.9-8050020210811100211.d428a79b2021-11-09redhat
redhatpython38-devel:3.8-8050020210811101222.e3d35cca2021-11-09redhat
redhatpython-pip-0:9.0.3-20.el82021-11-09redhat
redhatrh-python38-python-urllib3-0:1.25.7-7.el72021-08-24redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
python-pip—20.3.4-2—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
python-pip—20.3.4-2—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
python-pip—20.3.4-2—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
python-pip—20.3.4-2—
PyPI(1)
PackageVulnerable rangeFixed inDependents
pip0.2 ... 9.0.3 (102 versions)21.1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 33× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 155 total refreshes for this CVE.

  1. 2026-09-07 15:58 UTCEPSS rescore
  2. 2026-09-06 13:45 UTCEPSS rescore
  3. 2026-09-05 15:25 UTCEPSS rescore
  4. 2026-09-04 13:57 UTCEPSS rescore
  5. 2026-09-04 05:03 UTCEPSS rescore
  6. 2026-09-02 14:09 UTCEPSS rescore
  7. 2026-09-01 13:50 UTCEPSS rescore
  8. 2026-09-01 03:33 UTCEPSS rescore
  9. 2026-08-30 19:14 UTCEPSS rescore
  10. 2026-08-30 19:14 UTCEPSS rescore
  11. 2026-08-30 01:19 UTCEPSS rescore
  12. 2026-08-28 21:37 UTCEPSS rescore
  13. 2026-08-27 14:22 UTCEPSS rescore
  14. 2026-08-26 14:43 UTCEPSS rescore
  15. 2026-08-25 16:34 UTCEG score recompute
  16. 2026-08-25 16:34 UTCVendor advisory
  17. 2026-08-25 13:46 UTCEPSS rescore
  18. 2026-08-24 14:13 UTCEPSS rescore
  19. 2026-08-23 00:16 UTCEPSS rescore
  20. 2026-08-21 23:46 UTCEPSS rescore
  21. 2026-08-20 22:52 UTCEPSS rescore
  22. 2026-08-20 22:52 UTCEPSS rescore
  23. 2026-08-19 17:01 UTCEPSS rescore
  24. 2026-08-19 15:02 UTCOSV refresh
  25. 2026-08-18 13:45 UTCEPSS rescore
Show 75 more
  1. 2026-08-17 13:44 UTCEPSS rescore
  2. 2026-08-16 14:53 UTCEPSS rescore
  3. 2026-08-16 02:11 UTCEPSS rescore
  4. 2026-08-15 01:27 UTCEPSS rescore
  5. 2026-08-13 21:57 UTCEPSS rescore
  6. 2026-08-12 13:48 UTCEPSS rescore
  7. 2026-08-11 13:38 UTCEPSS rescore
  8. 2026-08-09 13:44 UTCEPSS rescore
  9. 2026-08-08 16:33 UTCEPSS rescore
  10. 2026-08-07 16:24 UTCEPSS rescore
  11. 2026-08-06 13:44 UTCEPSS rescore
  12. 2026-08-05 19:14 UTCEPSS rescore
  13. 2026-08-04 10:57 UTCOSV refresh
  14. 2026-08-04 10:34 UTCEPSS rescore
  15. 2026-08-03 10:33 UTCEPSS rescore
  16. 2026-08-02 02:24 UTCEPSS rescore
  17. 2026-08-01 04:13 UTCEPSS rescore
  18. 2026-07-30 16:25 UTCEPSS rescore
  19. 2026-07-30 01:28 UTCEPSS rescore
  20. 2026-07-28 15:33 UTCEPSS rescore
  21. 2026-07-26 14:52 UTCEPSS rescore
  22. 2026-07-26 14:52 UTCEPSS rescore
  23. 2026-07-25 14:15 UTCEPSS rescore
  24. 2026-07-24 14:15 UTCEPSS rescore
  25. 2026-07-23 14:16 UTCEPSS rescore
  26. 2026-07-23 02:02 UTCEG score recompute
  27. 2026-07-22 22:49 UTCEG score recompute
  28. 2026-07-22 14:06 UTCEPSS rescore
  29. 2026-07-21 15:22 UTCEPSS rescore
  30. 2026-07-21 15:22 UTCEPSS rescore
  31. 2026-07-20 17:05 UTCEPSS rescore
  32. 2026-07-19 14:29 UTCEPSS rescore
  33. 2026-07-19 02:27 UTCEPSS rescore
  34. 2026-07-18 10:02 UTCEPSS rescore
  35. 2026-07-18 10:02 UTCEPSS rescore
  36. 2026-07-18 07:59 UTCOSV refresh
  37. 2026-07-16 17:00 UTCEPSS rescore
  38. 2026-07-16 17:00 UTCEPSS rescore
  39. 2026-07-15 16:55 UTCEPSS rescore
  40. 2026-07-15 16:55 UTCEPSS rescore
  41. 2026-07-15 01:58 UTCEPSS rescore
  42. 2026-07-13 22:27 UTCEPSS rescore
  43. 2026-07-13 22:27 UTCEPSS rescore
  44. 2026-07-12 05:44 UTCEPSS rescore
  45. 2026-07-11 08:25 UTCEPSS rescore
  46. 2026-07-11 08:25 UTCEPSS rescore
  47. 2026-07-09 19:07 UTCEPSS rescore
  48. 2026-07-08 15:12 UTCEPSS rescore
  49. 2026-07-07 13:43 UTCEPSS rescore
  50. 2026-07-06 16:25 UTCEPSS rescore
  51. 2026-07-06 16:25 UTCEPSS rescore
  52. 2026-07-06 02:21 UTCEPSS rescore
  53. 2026-07-06 02:21 UTCEPSS rescore
  54. 2026-07-05 02:28 UTCEPSS rescore
  55. 2026-07-05 02:28 UTCEPSS rescore
  56. 2026-07-04 06:29 UTCEPSS rescore
  57. 2026-07-04 06:29 UTCEPSS rescore
  58. 2026-07-02 16:57 UTCEPSS rescore
  59. 2026-07-01 15:04 UTCEPSS rescore
  60. 2026-06-30 23:20 UTCEPSS rescore
  61. 2026-06-30 23:20 UTCEPSS rescore
  62. 2026-06-30 06:00 UTCOSV refresh
  63. 2026-06-29 14:04 UTCEPSS rescore
  64. 2026-06-28 14:05 UTCEPSS rescore
  65. 2026-06-28 04:54 UTCEPSS rescore
  66. 2026-06-28 04:54 UTCEPSS rescore
  67. 2026-06-27 03:06 UTCEPSS rescore
  68. 2026-06-27 03:06 UTCEPSS rescore
  69. 2026-06-25 13:48 UTCEPSS rescore
  70. 2026-06-25 13:48 UTCEPSS rescore
  71. 2026-06-24 14:03 UTCEPSS rescore
  72. 2026-06-24 14:03 UTCEPSS rescore
  73. 2026-06-23 21:31 UTCEPSS rescore
  74. 2026-06-23 21:31 UTCEPSS rescore
  75. 2026-06-22 14:24 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCfrenzymadness/CVE-2021-3572
    First seen Jun 7, 2021

    A simple repository helping to test CVE-2021-3572 in PyPA/pip

    Open source ↗

Frequently asked(5)

What is CVE-2021-3572?
CVE-2021-3572 is a medium vulnerability published on November 10, 2021. A flaw was found in python-pip in the way it handled Unicode separators in git references. A remote attacker could possibly use this issue to install a different revision on a repository. The highest threat from this vulnerability is to data integrity. This is fixed in python-pip version 21.1.
When was CVE-2021-3572 disclosed?
CVE-2021-3572 was first published in the National Vulnerability Database on November 10, 2021, with the most recent update on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2021-3572 actively exploited?
CVE-2021-3572 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2% probability of exploitation in the next 30 days, which ranks it in the top 22.6% of all scored CVEs.
What is the CVSS score of CVE-2021-3572?
CVE-2021-3572 has a CVSS v3 base score of 5.7 (NVD).
How do I remediate CVE-2021-3572?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2021-3572, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2021-3572

Explore →

Is Your Infrastructure Affected by CVE-2021-3572?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs