CVE-2016-5427

HIGHNVD 7.58.4▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.4 because EPSS predicts 63% probability of exploitation within the next 30 days (top 0.9% 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
8.4EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 63%
CISA-KEV: Not listedEPSS PROB: 63%CVSS: 7.5Exploit: Elevated riskExposed: 0

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

PowerDNS (aka pdns) Authoritative Server before 3.4.10 does not properly handle a . (dot) inside labels, which allows remote attackers to cause a denial of service (backend CPU consumption) via a crafted DNS query.

CVSS v3
7.5
EG Score
8.4(high)
EG Risk
67(Track)
EG Risk 67/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
Severity84% × 45%
Exploitation63% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
63%
EPSS %ILE
99%
KEV
Not listed

Published

September 21, 2016

Last Modified

June 17, 2026

References (12)

Affected Packages

(6 across 6 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
pdns—4.0.0~alpha1-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
pdns—4.0.0~alpha1-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
pdns—4.0.0~alpha1-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
pdns—4.0.0~alpha1-1—
Debian:7(1)
PackageVulnerable rangeFixed inDependents
pdns3.1-4, 3.1-4.1, 3.1-4.1+deb7u13.1-4.1+deb7u2—
Debian:8(1)
PackageVulnerable rangeFixed inDependents
pdns3.4.1-4 ... 3.4.1-4+deb8u5 (7 versions)3.4.1-4+deb8u6—

Weakness Classification(1)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2016-5427?
CVE-2016-5427 is a high vulnerability published on September 21, 2016. PowerDNS (aka pdns) Authoritative Server before 3.4.10 does not properly handle a . (dot) inside labels, which allows remote attackers to cause a denial of service (backend CPU consumption) via a crafted DNS query.
When was CVE-2016-5427 disclosed?
CVE-2016-5427 was first published in the National Vulnerability Database on September 21, 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-5427 actively exploited?
CVE-2016-5427 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 63% probability of exploitation in the next 30 days, which ranks it in the top 0.8% of all scored CVEs.
What is the CVSS score of CVE-2016-5427?
CVE-2016-5427 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.4.
How do I remediate CVE-2016-5427?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-5427, 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-5427

Explore →

Is Your Infrastructure Affected by CVE-2016-5427?

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

Start Free Scan →Browse All CVEs