CVE-2016-3105

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 2.7%, top 16% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 3%CVSS: 8.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The convert extension in Mercurial before 3.8 might allow context-dependent attackers to execute arbitrary code via a crafted git repository name.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
45(Track)
EG Risk 45/100SSVC: Track

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
Severity88% × 45%
Exploitation3% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
3%
EPSS %ILE
85%
KEV
Not listed

Published

May 9, 2016

Last Modified

June 17, 2026

Advisory Details (6)

Auto-updated May 10, 2026
No patch confirmed yet.
generic
http://www.securityfocus.com/bid/90536
generic

[SECURITY] [DSA 3570-1] mercurial security update

http://www.debian.org/security/2016/dsa-3570
generic

WhatsNew - Mercurial

https://www.mercurial-scm.org/wiki/WhatsNew#Mercurial_3.8_.2F_3.8.1_.282016-5-1.29
generic

Mercurial: a56296f55a5e

https://selenic.com/hg/rev/a56296f55a5e
generic

Mercurial: Multiple vulnerabilities (GLSA 201612-19) — Gentoo security

https://security.gentoo.org/glsa/201612-19
generic

The Slackware Linux Project: Slackware Security Advisories

http://www.slackware.com/security/viewer.php?l=slackware-security&y=2016&m=slackware-security.533255

Affected Packages

(7 across 7 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
mercurial—3.8.1-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
mercurial—3.8.1-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
mercurial—3.8.1-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
mercurial—3.8.1-1—
Debian:7(1)
PackageVulnerable rangeFixed inDependents
mercurial2.2.2-3, 2.2.2-4, 2.2.2-4+deb7u1, 2.2.2-4+deb7u22.2.2-4+deb7u3—
Debian:8(1)
PackageVulnerable rangeFixed inDependents
mercurial3.1.2-2, 3.1.2-2+deb8u1, 3.1.2-2+deb8u23.1.2-2+deb8u3—
PyPI(1)
PackageVulnerable rangeFixed inDependents
mercurial0.8.1 ... 3.7.3 (103 versions)3.8-rc—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 24× 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 124 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2016-3105?
CVE-2016-3105 is a high vulnerability published on May 9, 2016. The convert extension in Mercurial before 3.8 might allow context-dependent attackers to execute arbitrary code via a crafted git repository name.
When was CVE-2016-3105 disclosed?
CVE-2016-3105 was first published in the National Vulnerability Database on May 9, 2016, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2016-3105 actively exploited?
CVE-2016-3105 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3% probability of exploitation in the next 30 days, which ranks it in the top 15.5% of all scored CVEs.
What is the CVSS score of CVE-2016-3105?
CVE-2016-3105 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2016-3105?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-3105, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2016-3105

Explore →

Is Your Infrastructure Affected by CVE-2016-3105?

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

Start Free Scan →Browse All CVEs