CVE-2016-8622

CRITICALNVD 3.79.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-05-14. NVD baseline CVSS 3.7; sources differ by 6.1.

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

Also known asEUVD-2016-9467 (ENISA EUVD) · GHSA-xfmx-53v5-938g (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 4.7%CVSS: 3.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The URL percent-encoding decode function in libcurl before 7.51.0 is called curl_easy_unescape. Internally, even if this function would be made to allocate a unscape destination buffer larger than 2GB, it would return that new length in a signed 32 bit integer variable, thus the length would get either just truncated or both truncated and turned negative. That could then lead to libcurl writing outside of its heap based buffer.

CVSS v3
3.7
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.
Exploitation4.7% × 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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
4.7%
EPSS %ILE
91st
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
4.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-02). 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 every mission impact level.CISA BOD 26-04: 60 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 every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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

July 31, 2018

Last Modified

November 21, 2024

References (9)

Vendor Advisories for CVE-2016-8622(1)

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
ubuntulibcurl3-nss (7.50.1-1ubuntu1.1) @ yakkety2026-11-03ubuntu
redhathttpd24-nghttp2-0:1.7.1-7.el72018-11-13redhat
redhatjbcs-httpd24-curl2018-08-16redhat

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

(29 across 29 ecosystems)
Alpine:v3.10(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.51.0-r0: fixed in 7.51.0-r0
—
Alpine:v3.11(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.51.0: fixed in 7.51.0
—
Alpine:v3.12(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.51.0-r0: fixed in 7.51.0-r0
—
Alpine:v3.13(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.51.0-r0: fixed in 7.51.0-r0
—
Alpine:v3.14(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.51.0-r0: fixed in 7.51.0-r0
—
Alpine:v3.15(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.51.0-r0: fixed in 7.51.0-r0
—
Alpine:v3.16(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.51.0-r0: fixed in 7.51.0-r0
—
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.51.0-r0: fixed in 7.51.0-r0
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.51.0-r0: fixed in 7.51.0-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.51.0-r0: fixed in 7.51.0-r0
—
Alpine:v3.2(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.49.1-r4: fixed in 7.49.1-r4
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.51.0-r0: fixed in 7.51.0-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.51.0-r0: fixed in 7.51.0-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.51.0-r0: fixed in 7.51.0-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.51.0-r0: fixed in 7.51.0-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.51.0-r0: fixed in 7.51.0-r0
—
Alpine:v3.3(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.49.1-r4: fixed in 7.49.1-r4
—
Alpine:v3.4(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.51.0-r0: fixed in 7.51.0-r0
—
Alpine:v3.5(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.51.0-r0: fixed in 7.51.0-r0
—
Alpine:v3.6(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.51.0: fixed in 7.51.0
—
Alpine:v3.7(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.51.0: fixed in 7.51.0
—
Alpine:v3.8(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.51.0: fixed in 7.51.0
—
Alpine:v3.9(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.51.0-r0: fixed in 7.51.0-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.51.0-1: fixed in 7.51.0-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.51.0-1: fixed in 7.51.0-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.51.0-1: fixed in 7.51.0-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 7.51.0-1: fixed in 7.51.0-1
—
Debian:7(1)
PackageVulnerable rangeFix by version rangeDependents
curl7.26.0-1+wheezy10 ... 7.26.0-1+wheezy9 (15 versions)
  • every version up to 7.26.0-1+wheezy17: fixed in 7.26.0-1+wheezy17
—
Debian:8(1)
PackageVulnerable rangeFix by version rangeDependents
curl7.38.0-4, 7.38.0-4+deb8u1, 7.38.0-4+deb8u2, 7.38.0-4+deb8u3, 7.38.0-4+deb8u4
  • every version up to 7.38.0-4+deb8u5: fixed in 7.38.0-4+deb8u5
—

Weakness Classification(3)

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 28× in last 7d / 98× 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 99 of 244 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 145 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2016-8622?
CVE-2016-8622 is a critical-severity vulnerability; its CVE record was published on July 31, 2018. The URL percent-encoding decode function in libcurl before 7.51.0 is called curl_easy_unescape. Internally, even if this function would be made to allocate a unscape destination buffer larger than 2GB, it would return that new length in a signed 32 bit integer variable, thus the length would get…
When was CVE-2016-8622 made public?
CVE-2016-8622 was made public on November 2, 2016: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on July 31, 2018. EchelonGraph's copy of the record carries a last-modified date of November 21, 2024; the record at its source may have been updated since.
Is CVE-2016-8622 actively exploited?
CVE-2016-8622 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.7% probability of exploitation in the next 30 days (91st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2016-8622?
CVE-2016-8622 has a CVSS v3 base score of 3.7 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 9.8 (CRITICAL).
How do I remediate CVE-2016-8622?
A fix for CVE-2016-8622 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2016-8622 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-2016-8622

Explore →

Is Your Infrastructure Affected by CVE-2016-8622?

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