CVE-2016-8616

LOWNVD 3.75.9▲
EchelonGraph scoreMEDIUM confidence

Score 5.9 from GitHub Security Advisory published 2022-05-13. NVD baseline CVSS 3.7; sources differ by 2.2.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
3.7
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 3%CVSS: 3.7Exploit: NoneExposed: 0

A fix is available — apply it.

A flaw was found in curl before version 7.51.0 When re-using a connection, curl was doing case insensitive comparisons of user name and password with the existing connections. This means that if an unused connection with proper credentials exists for a protocol that has connection-scoped credentials, an attacker can cause that connection to be reused if s/he knows the case-insensitive version of the correct password.

CVSS v3
3.7
EG Score
5.9(medium)
EPSS
87.8%
KEV
Not listed

Published

August 1, 2018

Last Modified

November 21, 2024

References (20)

Vendor Advisories for CVE-2016-8616(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 / EcosystemFixed in / PatchReleasedSource
ubuntulibcurl3-nss (7.50.1-1ubuntu1.1) @ yakkety2026-05-28ubuntu
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.

Weakness Classification(2)

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

Frequently asked(5)

What is CVE-2016-8616?
CVE-2016-8616 is a low vulnerability published on August 1, 2018. A flaw was found in curl before version 7.51.0 When re-using a connection, curl was doing case insensitive comparisons of user name and password with the existing connections. This means that if an unused connection with proper credentials exists for a protocol that has connection-scoped…
When was CVE-2016-8616 disclosed?
CVE-2016-8616 was first published in the National Vulnerability Database on August 1, 2018, 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-2016-8616 actively exploited?
CVE-2016-8616 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 87.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2016-8616?
CVE-2016-8616 has a CVSS v3 base score of 3.7 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 5.9.
How do I remediate CVE-2016-8616?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-8616, 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

Explore the affected products and dependency analysis for CVE-2016-8616

Explore →

Is Your Infrastructure Affected by CVE-2016-8616?

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

Start Free Scan →Browse All CVEs