CVE-2021-22890

LOWNVD 3.73.7—
EchelonGraph scoreMEDIUM confidence

Score 3.7 from GitHub Security Advisory published 2022-05-24. NVD baseline CVSS 3.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
3.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 3.1%CVSS: 3.7Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

curl 7.63.0 to and including 7.75.0 includes vulnerability that allows a malicious HTTPS proxy to MITM a connection due to bad handling of TLS 1.3 session tickets. When using a HTTPS proxy and TLS 1.3, libcurl can confuse session tickets arriving from the HTTPS proxy but work as if they arrived from the remote server and then wrongly "short-cut" the host handshake. When confusing the tickets, a HTTPS proxy can trick libcurl to use the wrong session ticket resume for the host and thereby circumvent the server TLS certificate check and make a MITM attack to be possible to perform unnoticed. Note that such a malicious HTTPS proxy needs to provide a certificate that curl will accept for the MITMed server for an attack to work - unless curl has been told to ignore the server certificate check.

CVSS v3
3.7
EG Score
3.7LOWmedium confidence
EG Risk
33
EG Risk 33/100CISA SSVC

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
Severity37% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
3.1%
EPSS %ILE
87th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

April 1, 2021

Last Modified

June 9, 2025

References (18)

Vendor Advisories for CVE-2021-22890(3)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibcurl4-openssl-dev (7.47.0-1ubuntu2.19) @ xenial2026-05-26ubuntu
redhatjbcs-httpd24-curl2021-06-17redhat
redhatjbcs-httpd24-mod_security-0:2.9.2-63.GA.jbcs.el72021-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

(18 across 18 ecosystems)
Alpine:v3.12(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.76.0-r0: fixed in 7.76.0-r0
—
Alpine:v3.13(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.76.0-r0: fixed in 7.76.0-r0
—
Alpine:v3.14(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.76.0-r0: fixed in 7.76.0-r0
—
Alpine:v3.15(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.76.0-r0: fixed in 7.76.0-r0
—
Alpine:v3.16(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.76.0-r0: fixed in 7.76.0-r0
—
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.76.0-r0: fixed in 7.76.0-r0
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.76.0-r0: fixed in 7.76.0-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.76.0-r0: fixed in 7.76.0-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.76.0-r0: fixed in 7.76.0-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.76.0-r0: fixed in 7.76.0-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.76.0-r0: fixed in 7.76.0-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.76.0-r0: fixed in 7.76.0-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.76.0-r0: fixed in 7.76.0-r0
—
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
curl7.64.0-4, 7.64.0-4+deb10u1
  • every version up to 7.64.0-4+deb10u2: fixed in 7.64.0-4+deb10u2
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.74.0-1.2: fixed in 7.74.0-1.2
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.74.0-1.2: fixed in 7.74.0-1.2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.74.0-1.2: fixed in 7.74.0-1.2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.74.0-1.2: fixed in 7.74.0-1.2
—

Weakness Classification(2)

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

Additional Vendor Advisories

(1)

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 8× in last 7d / 32× 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 180 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2021-22890?
CVE-2021-22890 is a low vulnerability published on April 1, 2021. curl 7.63.0 to and including 7.75.0 includes vulnerability that allows a malicious HTTPS proxy to MITM a connection due to bad handling of TLS 1.3 session tickets. When using a HTTPS proxy and TLS 1.3, libcurl can confuse session tickets arriving from the HTTPS proxy but work as if they arrived…
When was CVE-2021-22890 disclosed?
CVE-2021-22890 was first published on April 1, 2021, with the most recent update on June 9, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2021-22890 actively exploited?
CVE-2021-22890 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.1% probability of exploitation in the next 30 days (87th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2021-22890?
CVE-2021-22890 has a CVSS v3 base score of 3.7 (NVD).
How do I remediate CVE-2021-22890?
A fix for CVE-2021-22890 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2021-22890 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-22890

Explore →

Is Your Infrastructure Affected by CVE-2021-22890?

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

Book a Demo →Browse All CVEs