CVE-2021-22901

HIGHNVD 8.18.6
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 8.6 because EPSS predicted 64% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs) when EchelonGraph scored this CVE. NVD baseline CVSS 8.1 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekElevated

Also known asEUVD-2021-10033 (ENISA EUVD) · GHSA-vjwf-ghhc-2p8q (GitHub Security Advisories)Source: ENISA EUVD

8.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 64%
CISA-KEV: Not listedEPSS PROB: 64%CVSS: 8.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

curl 7.75.0 through 7.76.1 suffers from a use-after-free vulnerability resulting in already freed memory being used when a TLS 1.3 session ticket arrives over a connection. A malicious server can use this in rare unfortunate circumstances to potentially reach remote code execution in the client. When libcurl at run-time sets up support for TLS 1.3 session tickets on a connection using OpenSSL, it stores pointers to the transfer in-memory object for later retrieval when a session ticket arrives. If the connection is used by multiple transfers (like with a reused HTTP/1.1 connection or multiplexed HTTP/2 connection) that first transfer object might be freed before the new session is established on that connection and then the function will access a memory buffer that might be freed. When using that memory, libcurl might even call a function pointer in the object, making it possible for a remote code execution if the server could somehow manage to get crafted memory content into the correct place in memory.

CVSS v3
8.1
EG Score
8.6HIGHhigh confidence
EG Risk
77
EG Risk 77/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation64% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
64%
EPSS %ILE
99th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.6): severity, escalated by confirmed exploitation. This CVE's 8.6 is EPSS's lift toward 9.0 from its impact severity (EG Severity, CVSS 8.1 HIGH): a likelihood of exploitation, not impact.

EG Severity
8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
64% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 11, 2021

Last Modified

October 14, 2026

Advisory Details (7)

Auto-updated Sep 16, 2026
Patch available. Sources: github_commit.
GitHub commit

commit 7f4a9a9b2a49 (curl/curl)

Fix landed in curl/curl commit 7f4a9a9b2a49 — awaiting tagged release

https://github.com/curl/curl/commit/7f4a9a9b2a49547eae24d2e19bc5c346e9026479
Web page

curl - TLS session caching disaster - CVE-2021-22901

https://curl.se/docs/CVE-2021-22901.html

Vendor Advisories for CVE-2021-22901(4)

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

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatjbcs-httpd24-mod_security-0:2.9.2-63.GA.jbcs.el72021-06-17redhat
redhatjbcs-httpd24-curl2021-06-17redhat

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

(13 across 13 ecosystems)
Alpine:v3.12(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.75.0 up to 7.77.0-r0: fixed in 7.77.0-r0
—
Alpine:v3.13(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.75.0 up to 7.77.0-r0: fixed in 7.77.0-r0
—
Alpine:v3.14(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.75.0 up to 7.77.0-r0: fixed in 7.77.0-r0
—
Alpine:v3.15(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.75.0 up to 7.77.0-r0: fixed in 7.77.0-r0
—
Alpine:v3.16(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.75.0 up to 7.77.0-r0: fixed in 7.77.0-r0
—
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.75.0 up to 7.77.0-r0: fixed in 7.77.0-r0
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.75.0 up to 7.77.0-r0: fixed in 7.77.0-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.75.0 up to 7.77.0-r0: fixed in 7.77.0-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.75.0 up to 7.77.0-r0: fixed in 7.77.0-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.75.0 up to 7.77.0-r0: fixed in 7.77.0-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.75.0 up to 7.77.0-r0: fixed in 7.77.0-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.75.0 up to 7.77.0-r0: fixed in 7.77.0-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • 7.75.0 up to 7.77.0-r0: fixed in 7.77.0-r0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 40× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 94 of 179 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 6 repeat rows among the latest 100 are merged into the row they repeat. The 85 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2021-22901?
CVE-2021-22901 is a high-severity vulnerability; its CVE record was published on June 11, 2021. curl 7.75.0 through 7.76.1 suffers from a use-after-free vulnerability resulting in already freed memory being used when a TLS 1.3 session ticket arrives over a connection. A malicious server can use this in rare unfortunate circumstances to potentially reach remote code execution in the client.…
When was the CVE record for CVE-2021-22901 published?
The CVE record for CVE-2021-22901 was published on June 11, 2021. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 14, 2026; the record at its source may have been updated since.
Is CVE-2021-22901 actively exploited?
CVE-2021-22901 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 64% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2021-22901?
CVE-2021-22901 has a CVSS v3 base score of 8.1 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 8.6 (HIGH).
How do I remediate CVE-2021-22901?
A fix for CVE-2021-22901 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2021-22901 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2021-22901?

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