CVE-2016-2776

CRITICALNVD 7.59.0▲
EchelonGraph scoreHIGH confidence

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

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Weaponized
9.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 89%
  • Public exploit code is available (Metasploit, epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 89%CVSS: 7.5Exploit: Metasploit · epss top5pct · epss high · public exploitExposed: 0

A fix is available — apply it.

buffer.c in named in ISC BIND 9 before 9.9.9-P3, 9.10.x before 9.10.4-P3, and 9.11.x before 9.11.0rc3 does not properly construct responses, which allows remote attackers to cause a denial of service (assertion failure and daemon exit) via a crafted query.

CVSS v3
7.5
EG Score
9.0(high)
EG Risk
81(Track)
EG Risk 81/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
Severity90% × 45%
Exploitation89% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
89%
EPSS %ILE
100%
KEV
Not listed

Published

September 28, 2016

Last Modified

June 17, 2026

References (34)

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulwresd (1:9.10.3.dfsg.P4-8ubuntu1.1) @ xenial2026-05-22ubuntu
redhatbind-32:9.8.2-0.37.rc1.el6_7.82016-10-25redhat
redhatbind-32:9.9.4-29.el7_2.42016-09-28redhat
redhatbind97-32:9.7.0-21.P2.el5_11.72016-09-28redhat

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

(8 across 8 ecosystems)
Alpine:v3.2(1)
PackageVulnerable rangeFixed inDependents
bind9.10.0-r0 ... 9.9.5-r0 (61 versions)9.10.4_p3—
Alpine:v3.3(1)
PackageVulnerable rangeFixed inDependents
bind9.10.0-r0 ... 9.9.5-r0 (66 versions)9.10.4_p3-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
bind9—1:9.10.3.dfsg.P4-11—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
bind9—1:9.10.3.dfsg.P4-11—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
bind9—1:9.10.3.dfsg.P4-11—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
bind9—1:9.10.3.dfsg.P4-11—
Debian:7(1)
PackageVulnerable rangeFixed inDependents
bind91:9.8.4.dfsg.P1-6+nmu2 ... 1:9.8.4.dfsg.P1-6+nmu2+deb7u9 (13 versions)1:9.8.4.dfsg.P1-6+nmu2+deb7u11—
Debian:8(1)
PackageVulnerable rangeFixed inDependents
bind91:9.9.5.dfsg-9 ... 1:9.9.5.dfsg-9+deb8u6 (7 versions)1:9.9.5.dfsg-9+deb8u7—

Weakness Classification(1)

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

All Vendor Advisories

(4)

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

Publicly available exploits

(3 references)

Working exploit code is in the public domain (1 Metasploit module) (1 GitHub PoC) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-40453
    First seen Oct 4, 2016

    ISC BIND 9 - Denial of Service

    Open source ↗
  • GitHub PoCinfobyte/CVE-2016-2776
    First seen Sep 30, 2016

    CVE-2016-2776

    Open source ↗
  • Metasploitauxiliary/dos/dns/bind_tsig✓ verified
    First seen Sep 27, 2016

    BIND TSIG Query Denial of Service

    Open source ↗

Related CVEs(same product + same vendor + same CWE)

Same vendor

1 shown

redhat:RHSA-2016:2099

Frequently asked(5)

What is CVE-2016-2776?
CVE-2016-2776 is a critical vulnerability published on September 28, 2016. buffer.c in named in ISC BIND 9 before 9.9.9-P3, 9.10.x before 9.10.4-P3, and 9.11.x before 9.11.0rc3 does not properly construct responses, which allows remote attackers to cause a denial of service (assertion failure and daemon exit) via a crafted query.
When was CVE-2016-2776 disclosed?
CVE-2016-2776 was first published in the National Vulnerability Database on September 28, 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-2776 actively exploited?
CVE-2016-2776 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 89% probability of exploitation in the next 30 days, which ranks it in the top 0.2% of all scored CVEs.
What is the CVSS score of CVE-2016-2776?
CVE-2016-2776 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2016-2776?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-2776, 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-2776

Explore →

Is Your Infrastructure Affected by CVE-2016-2776?

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

Book a Demo →Browse All CVEs