CVE-2022-42915

CRITICALNVD 8.19.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-10-30. NVD baseline CVSS 8.1; sources differ by 1.7.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2022-45972 (ENISA EUVD) · GHSA-98w6-hw73-ph8m (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 3.7%CVSS: 8.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

curl before 7.86.0 has a double free. If curl is told to use an HTTP proxy for a transfer with a non-HTTP(S) URL, it sets up the connection to the remote server by issuing a CONNECT request to the proxy, and then tunnels the rest of the protocol through. An HTTP proxy might refuse this request (HTTP proxies often only allow outgoing connections to specific port numbers, like 443 for HTTPS) and instead return a non-200 status code to the client. Due to flaws in the error/cleanup handling, this could trigger a double free in curl if one of the following schemes were used in the URL for the transfer: dict, gopher, gophers, ldap, ldaps, rtmp, rtmps, or telnet. The earliest affected version is 7.77.0.

CVSS v3
8.1
EG Score
9.8CRITICALmedium confidence
EG Risk
46
EG Risk 46/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation3.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
3.7%
EPSS %ILE
89th
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
3.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade 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; Track* at high (mission-essential systems).

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

Exploitation none (CISA Vulnrichment) · Automatable no (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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

October 29, 2022

Last Modified

October 14, 2026

Advisory Details (10)

Auto-updated Sep 18, 2026
Patch available.
Web page

About the security content of macOS Ventura 13.2 - Apple Support

https://support.apple.com/kb/HT213605
Web page

About the security content of macOS Monterey 12.6.3 - Apple Support

https://support.apple.com/kb/HT213604
Web page

curl: Multiple Vulnerabilities (GLSA 202212-01) — Gentoo security

https://security.gentoo.org/glsa/202212-01
Web page

[SECURITY] Fedora 35 Update: curl-7.79.1-7.fc35 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/Q27V5YYMXUVI6PRZQVECON32XPVWTKDK/
Web page

[SECURITY] Fedora 36 Update: curl-7.82.0-9.fc36 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HVU3IMZCKR4VE6KJ4GCWRL2ILLC6OV76/
Web page

[SECURITY] Fedora 37 Update: curl-7.85.0-2.fc37 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/37YEVVC6NAF6H7UHH6YAUY5QEVY6LIH2/
Web page

curl - HTTP proxy double free - CVE-2022-42915

https://curl.se/docs/CVE-2022-42915.html
Web page

Full Disclosure: APPLE-SA-2023-01-23-5 macOS Monterey 12.6.3

http://seclists.org/fulldisclosure/2023/Jan/20
Web page

Full Disclosure: APPLE-SA-2023-01-23-4 macOS Ventura 13.2

http://seclists.org/fulldisclosure/2023/Jan/19

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntucurl (7.85.0-1ubuntu0.1) @ kinetic2026-10-30ubuntu
redhatjbcs-httpd24-curl2022-12-08redhat
redhatjbcs-httpd24-curl-0:7.86.0-2.el7jbcs2022-12-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

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

Weakness Classification(1)

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 27× in last 7d / 96× 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 100 of 264 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. None are among the latest 100 rows. The 164 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 03:06 UTCEG score recompute
  2. 2026-11-02 03:06 UTCVendor advisory
  3. 2026-11-02 03:05 UTCGHSA enrichmentGHSA-98w6-hw73-ph8m · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-11-01 16:30 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  5. 2026-11-01 03:19 UTCEG score recompute
  6. 2026-11-01 03:19 UTCVendor advisory
  7. 2026-11-01 03:19 UTCGHSA enrichmentGHSA-98w6-hw73-ph8m · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-10-31 16:29 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  9. 2026-10-31 03:33 UTCEG score recompute
  10. 2026-10-31 03:33 UTCVendor advisory
  11. 2026-10-31 03:33 UTCGHSA enrichmentGHSA-98w6-hw73-ph8m · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-10-30 16:30 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  13. 2026-10-30 03:47 UTCEG score recompute
  14. 2026-10-30 03:47 UTCVendor advisory
  15. 2026-10-30 03:47 UTCGHSA enrichmentGHSA-98w6-hw73-ph8m · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-29 16:29 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  17. 2026-10-29 04:01 UTCEG score recompute
  18. 2026-10-29 04:01 UTCGHSA enrichmentGHSA-98w6-hw73-ph8m · GitHub severity CRITICAL · GitHub CVSS 9.8
  19. 2026-10-28 16:28 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  20. 2026-10-28 04:15 UTCEG score recompute
  21. 2026-10-28 04:15 UTCVendor advisory
  22. 2026-10-28 04:15 UTCGHSA enrichmentGHSA-98w6-hw73-ph8m · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-10-27 16:28 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  24. 2026-10-27 04:18 UTCEG score recompute
  25. 2026-10-27 04:18 UTCVendor advisory
Show 75 more
  1. 2026-10-27 04:18 UTCGHSA enrichmentGHSA-98w6-hw73-ph8m · GitHub severity CRITICAL · GitHub CVSS 9.8
  2. 2026-10-26 16:28 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  3. 2026-10-26 00:07 UTCVendor advisory
  4. 2026-10-26 00:07 UTCGHSA enrichmentGHSA-98w6-hw73-ph8m · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-10-25 17:59 UTCEG score recompute
  6. 2026-10-25 16:29 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  7. 2026-10-25 00:21 UTCEG score recompute
  8. 2026-10-25 00:21 UTCVendor advisory
  9. 2026-10-25 00:21 UTCGHSA enrichmentGHSA-98w6-hw73-ph8m · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-10-24 16:29 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  11. 2026-10-24 00:36 UTCEG score recompute
  12. 2026-10-24 00:36 UTCVendor advisory
  13. 2026-10-24 00:36 UTCGHSA enrichmentGHSA-98w6-hw73-ph8m · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-10-23 16:28 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  15. 2026-10-23 00:49 UTCEG score recompute
  16. 2026-10-23 00:49 UTCVendor advisory
  17. 2026-10-23 00:49 UTCGHSA enrichmentGHSA-98w6-hw73-ph8m · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-22 16:30 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  19. 2026-10-22 01:02 UTCEG score recompute
  20. 2026-10-22 01:02 UTCVendor advisory
  21. 2026-10-22 01:02 UTCGHSA enrichmentGHSA-98w6-hw73-ph8m · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-10-21 16:29 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  23. 2026-10-21 01:15 UTCEG score recompute
  24. 2026-10-21 01:15 UTCVendor advisory
  25. 2026-10-21 01:15 UTCGHSA enrichmentGHSA-98w6-hw73-ph8m · GitHub severity CRITICAL · GitHub CVSS 9.8
  26. 2026-10-20 16:29 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  27. 2026-10-20 01:29 UTCEG score recompute
  28. 2026-10-20 01:29 UTCVendor advisory
  29. 2026-10-20 01:28 UTCGHSA enrichmentGHSA-98w6-hw73-ph8m · GitHub severity CRITICAL · GitHub CVSS 9.8
  30. 2026-10-19 16:28 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  31. 2026-10-19 00:23 UTCEG score recompute
  32. 2026-10-19 00:23 UTCVendor advisory
  33. 2026-10-19 00:23 UTCGHSA enrichmentGHSA-98w6-hw73-ph8m · GitHub severity CRITICAL · GitHub CVSS 9.8
  34. 2026-10-18 16:28 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  35. 2026-10-18 08:25 UTCEG score recompute
  36. 2026-10-18 00:37 UTCEG score recompute
  37. 2026-10-18 00:37 UTCVendor advisory
  38. 2026-10-18 00:37 UTCGHSA enrichmentGHSA-98w6-hw73-ph8m · GitHub severity CRITICAL · GitHub CVSS 9.8
  39. 2026-10-17 16:29 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  40. 2026-10-17 00:48 UTCEG score recompute
  41. 2026-10-17 00:48 UTCVendor advisory
  42. 2026-10-17 00:48 UTCGHSA enrichmentGHSA-98w6-hw73-ph8m · GitHub severity CRITICAL · GitHub CVSS 9.8
  43. 2026-10-16 16:35 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  44. 2026-10-16 00:49 UTCEG score recompute
  45. 2026-10-16 00:49 UTCVendor advisory
  46. 2026-10-16 00:48 UTCGHSA enrichmentGHSA-98w6-hw73-ph8m · GitHub severity CRITICAL · GitHub CVSS 9.8
  47. 2026-10-15 16:28 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  48. 2026-10-14 19:28 UTCVendor advisory
  49. 2026-10-14 19:28 UTCGHSA enrichmentGHSA-98w6-hw73-ph8m · GitHub severity CRITICAL · GitHub CVSS 9.8
  50. 2026-10-14 18:37 UTCEG score recompute
  51. 2026-10-14 18:37 UTCVendor advisory
  52. 2026-10-14 18:37 UTCGHSA enrichmentGHSA-98w6-hw73-ph8m · GitHub severity CRITICAL · GitHub CVSS 9.8
  53. 2026-10-14 16:29 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  54. 2026-10-13 17:50 UTCEG score recompute
  55. 2026-10-13 17:50 UTCVendor advisory
  56. 2026-10-13 17:49 UTCGHSA enrichmentGHSA-98w6-hw73-ph8m · GitHub severity CRITICAL · GitHub CVSS 9.8
  57. 2026-10-13 16:29 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  58. 2026-10-12 18:02 UTCEG score recompute
  59. 2026-10-12 18:02 UTCVendor advisory
  60. 2026-10-12 18:01 UTCGHSA enrichmentGHSA-98w6-hw73-ph8m · GitHub severity CRITICAL · GitHub CVSS 9.8
  61. 2026-10-12 16:30 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  62. 2026-10-11 22:09 UTCEG score recompute
  63. 2026-10-11 13:44 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  64. 2026-10-10 19:57 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  65. 2026-10-09 20:04 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  66. 2026-10-08 17:05 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  67. 2026-10-07 23:45 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  68. 2026-10-06 15:14 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  69. 2026-10-05 17:40 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  70. 2026-10-04 23:19 UTCEPSS rescoreEPSS 2.9% · 86th percentile
  71. 2026-10-03 14:23 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  72. 2026-10-02 16:23 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  73. 2026-10-01 19:47 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  74. 2026-09-30 16:07 UTCEG score recompute
  75. 2026-09-30 15:01 UTCEPSS rescoreEPSS 3.1% · 87th percentile

Frequently asked(5)

What is CVE-2022-42915?
CVE-2022-42915 is a critical-severity vulnerability; its CVE record was published on October 29, 2022. curl before 7.86.0 has a double free. If curl is told to use an HTTP proxy for a transfer with a non-HTTP(S) URL, it sets up the connection to the remote server by issuing a CONNECT request to the proxy, and then tunnels the rest of the protocol through. An HTTP proxy might refuse this request…
When was the CVE record for CVE-2022-42915 published?
The CVE record for CVE-2022-42915 was published on October 29, 2022. 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-2022-42915 actively exploited?
CVE-2022-42915 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.7% probability of exploitation in the next 30 days (89th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-42915?
CVE-2022-42915 has a CVSS v3 base score of 8.1 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 9.8 (CRITICAL).
How do I remediate CVE-2022-42915?
A fix for CVE-2022-42915 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-42915 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-2022-42915

Explore →

Is Your Infrastructure Affected by CVE-2022-42915?

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