CVE-2021-32610

HIGHNVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under NVD CVSS v3. EPSS exploit probability: 73.4%, top 1% 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
Trending — 3 sources updated this weekElevated
7.1
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 73%
CISA-KEV: Not listedEPSS: 73%CVSS: 7.1Exploit: NoneExposed: 0

A fix is available — apply it.

In Archive_Tar before 1.4.14, symlinks can refer to targets outside of the extracted archive, a different vulnerability than CVE-2020-36193.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
—
EPSS
99.4%
KEV
Not listed

Published

July 30, 2021

Last Modified

November 21, 2024

References (18)

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuphp-pear (1:1.10.9+submodules+notgz-1.1ubuntu1.1) @ hirsute2026-05-26ubuntu
ubuntuphp-pear (1:1.10.1+submodules+notgz-6ubuntu0.3+esm1) @ xenial2026-05-26ubuntu
redhatphp:7.4-8070020220707122009.afd00e682022-11-08redhat

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

(2 across 1 ecosystem)
Packagist(2)
PackageVulnerable rangeFixed inDependents
drupal/core8.0.0 ... 9.2.1 (174 versions)9.2.2—
pear/archive_tar1.3.11 ... 1.4.9 (20 versions)1.4.14—

Weakness Classification(1)

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

All Vendor Advisories

(3)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 12× in last 7d / 30× 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.

  1. 2026-07-22 22:48 UTCEG score recompute
  2. 2026-07-22 14:06 UTCEPSS rescore
  3. 2026-07-22 14:06 UTCEPSS rescore
  4. 2026-07-21 15:22 UTCEPSS rescore
  5. 2026-07-21 15:22 UTCEPSS rescore
  6. 2026-07-20 17:05 UTCEPSS rescore
  7. 2026-07-19 02:27 UTCEPSS rescore
  8. 2026-07-18 15:29 UTCOSV refresh
  9. 2026-07-18 10:02 UTCEPSS rescore
  10. 2026-07-18 10:02 UTCEPSS rescore
  11. 2026-07-16 17:00 UTCEPSS rescore
  12. 2026-07-16 17:00 UTCEPSS rescore
  13. 2026-07-15 16:55 UTCEPSS rescore
  14. 2026-07-13 22:27 UTCEPSS rescore
  15. 2026-07-13 06:10 UTCEPSS rescore
  16. 2026-07-09 19:07 UTCEPSS rescore
  17. 2026-07-05 02:28 UTCEPSS rescore
  18. 2026-07-05 02:28 UTCEPSS rescore
  19. 2026-07-01 15:04 UTCEPSS rescore
  20. 2026-06-30 23:20 UTCEPSS rescore
  21. 2026-06-30 23:20 UTCEPSS rescore
  22. 2026-06-30 21:30 UTCOSV refresh
  23. 2026-06-29 14:04 UTCEPSS rescore
  24. 2026-06-27 03:06 UTCEPSS rescore
  25. 2026-06-25 13:48 UTCEPSS rescore
Show 49 more
  1. 2026-06-25 13:48 UTCEPSS rescore
  2. 2026-06-24 14:03 UTCEPSS rescore
  3. 2026-06-24 14:03 UTCEPSS rescore
  4. 2026-06-23 21:31 UTCEPSS rescore
  5. 2026-06-23 21:31 UTCEPSS rescore
  6. 2026-06-18 17:51 UTCEPSS rescore
  7. 2026-06-18 17:51 UTCEPSS rescore
  8. 2026-06-17 17:51 UTCEPSS rescore
  9. 2026-06-15 17:46 UTCEPSS rescore
  10. 2026-06-14 23:15 UTCEPSS rescore
  11. 2026-06-13 22:58 UTCEPSS rescore
  12. 2026-06-13 22:58 UTCEPSS rescore
  13. 2026-06-13 00:57 UTCOSV refresh
  14. 2026-06-12 23:10 UTCEPSS rescore
  15. 2026-06-12 23:10 UTCEPSS rescore
  16. 2026-06-11 13:58 UTCEPSS rescore
  17. 2026-06-10 22:16 UTCEPSS rescore
  18. 2026-06-10 13:20 UTCEPSS rescore
  19. 2026-06-08 14:15 UTCEPSS rescore
  20. 2026-06-08 14:15 UTCEPSS rescore
  21. 2026-06-07 15:23 UTCEPSS rescore
  22. 2026-06-07 15:23 UTCEPSS rescore
  23. 2026-06-06 13:46 UTCEPSS rescore
  24. 2026-06-06 13:46 UTCEPSS rescore
  25. 2026-06-06 13:46 UTCEPSS rescore
  26. 2026-06-05 22:45 UTCEPSS rescore
  27. 2026-06-05 06:09 UTCEPSS rescore
  28. 2026-06-05 06:09 UTCEPSS rescore
  29. 2026-06-04 13:10 UTCEPSS rescore
  30. 2026-06-04 13:10 UTCEPSS rescore
  31. 2026-06-02 20:11 UTCEPSS rescore
  32. 2026-06-02 20:11 UTCEPSS rescore
  33. 2026-06-01 13:50 UTCEPSS rescore
  34. 2026-06-01 13:50 UTCEPSS rescore
  35. 2026-05-31 00:15 UTCEPSS rescore
  36. 2026-05-31 00:15 UTCEPSS rescore
  37. 2026-05-29 13:42 UTCEPSS rescore
  38. 2026-05-29 13:42 UTCEPSS rescore
  39. 2026-05-28 13:43 UTCEPSS rescore
  40. 2026-05-28 13:43 UTCEPSS rescore
  41. 2026-05-27 13:39 UTCEPSS rescore
  42. 2026-05-27 13:39 UTCEPSS rescore
  43. 2026-05-27 13:39 UTCEPSS rescore
  44. 2026-05-26 13:42 UTCEPSS rescore
  45. 2026-05-26 12:55 UTCEG score recompute
  46. 2026-05-26 12:55 UTCVendor advisory
  47. 2026-05-26 07:17 UTCEPSS rescore
  48. 2026-05-26 07:17 UTCEPSS rescore
  49. 2026-05-26 07:17 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2021-32610?
CVE-2021-32610 is a high vulnerability published on July 30, 2021. In Archive_Tar before 1.4.14, symlinks can refer to targets outside of the extracted archive, a different vulnerability than CVE-2020-36193.
When was CVE-2021-32610 disclosed?
CVE-2021-32610 was first published in the National Vulnerability Database on July 30, 2021, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2021-32610 actively exploited?
CVE-2021-32610 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2021-32610?
CVE-2021-32610 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2021-32610?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2021-32610, 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-32610

Explore →

Is Your Infrastructure Affected by CVE-2021-32610?

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

Start Free Scan →Browse All CVEs