CVE-2016-2118

HIGHNVD 7.57.7▲
EchelonGraph scoreHIGH confidence

Score elevated to 7.7 because EPSS predicts 37% probability of exploitation within the next 30 days (top 1.6% of all CVEs). NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Elevated
7.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 37%CVSS: 7.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

The MS-SAMR and MS-LSAD protocol implementations in Samba 3.x and 4.x before 4.2.11, 4.3.x before 4.3.8, and 4.4.x before 4.4.2 mishandle DCERPC connections, which allows man-in-the-middle attackers to perform protocol-downgrade attacks and impersonate users by modifying the client-server data stream, aka "BADLOCK."

CVSS v3
7.5
EG Score
7.7(high)
EG Risk
55(Track)
EG Risk 55/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
Severity77% × 45%
Exploitation40% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
37%
EPSS %ILE
98%
KEV
Not listed

Published

April 12, 2016

Last Modified

June 17, 2026

References (90)

Patch Availability(12)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntusamba (2:4.3.8+dfsg-0ubuntu0.15.10.2) @ wily2026-05-22ubuntu
redhatsamba-0:4.2.10-5.ael7b_12016-04-13redhat
redhatsamba-0:4.2.10-6.el7_22016-04-13redhat
redhatsamba4-0:4.2.10-6.el6_62016-04-12redhat
redhatsamba-0:4.2.11-2.el7rhgs2016-04-12redhat
redhatsamba-0:3.0.33-3.37.el42016-04-12redhat
redhatsamba-0:3.0.33-3.40.el5_92016-04-12redhat
redhatsamba-0:3.6.23-30.el6_72016-04-12redhat
redhatsamba3x-0:3.6.23-12.el5_112016-04-12redhat
redhatsamba-0:3.0.33-3.41.el5_112016-04-12redhat
redhatsamba3x-0:3.6.23-12.el5_92016-04-12redhat
redhatsamba-0:3.6.23-30.el6_62016-04-12redhat

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

(6 across 6 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
samba—2:4.3.7+dfsg-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
samba—2:4.3.7+dfsg-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
samba—2:4.3.7+dfsg-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
samba—2:4.3.7+dfsg-1—
Debian:7(1)
PackageVulnerable rangeFixed inDependents
samba2:3.6.6-6 ... 2:3.6.6-6+deb7u8 (13 versions)2:3.6.6-6+deb7u9—
Debian:8(1)
PackageVulnerable rangeFixed inDependents
samba2:4.1.17+dfsg-2 ... 2:4.2.1+dfsg-1 (11 versions)2:4.2.10+dfsg-0+deb8u1—

Weakness Classification(1)

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

All Vendor Advisories

(12)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2016-2118?
CVE-2016-2118 is a high vulnerability published on April 12, 2016. The MS-SAMR and MS-LSAD protocol implementations in Samba 3.x and 4.x before 4.2.11, 4.3.x before 4.3.8, and 4.4.x before 4.4.2 mishandle DCERPC connections, which allows man-in-the-middle attackers to perform protocol-downgrade attacks and impersonate users by modifying the client-server data…
When was CVE-2016-2118 disclosed?
CVE-2016-2118 was first published in the National Vulnerability Database on April 12, 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-2118 actively exploited?
CVE-2016-2118 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 37% probability of exploitation in the next 30 days, which ranks it in the top 1.6% of all scored CVEs.
What is the CVSS score of CVE-2016-2118?
CVE-2016-2118 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.7.
How do I remediate CVE-2016-2118?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-2118, 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-2118

Explore →

Is Your Infrastructure Affected by CVE-2016-2118?

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

Start Free Scan →Browse All CVEs