CVE-2026-5172

HIGHPre-NVD 7.37.3
EchelonGraph scoreMEDIUM confidence

Score 7.3 from GitHub Security Advisory (severity: HIGH) published 2026-05-11. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 4 sources updated this week
7.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 3%CVSS: 7.3Exploit: None knownExposed: 0

A fix is available — apply it.

A buffer overflow in dnsmasq’s extract_addresses() function allows an attacker to trigger a heap out-of-bounds read and crash by exploiting a malformed DNS response, enabling extract_name() to advance the pointer past the record’s end.

CVSS v3
7.3
EG Score
7.3(medium)
EG Risk
34(Track)
EG Risk 34/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
Severity73% × 45%
Exploitation3% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
3%
EPSS %ILE
85%
KEV
Not listed

Published

May 11, 2026

Last Modified

September 1, 2026

Advisory Details (6)

Auto-updated Jun 9, 2026
Patch available. Sources: github_pr, github_release, cert.
cert

VU#471747 - dnsmasq contains several vulnerabilities, including attacker DNS redirect, privilege escalation, and heap manipulation

https://www.kb.cert.org/vuls/id/471747
generic

Index of /dnsmasq/CVE

https://thekelleys.org.uk/dnsmasq/CVE/
github_release Patch Available

Pi-hole FTL v6.6.2

Patch available: pi-hole/FTL v6.6.2

https://github.com/pi-hole/FTL/releases/tag/v6.6.2
github_pr

[Backport release-25.11] dnsmasq: 2.92 -> 2.92rel2

Fix merged in NixOS/nixpkgs PR #519093 on 2026-05-11 — awaiting tagged release

https://github.com/NixOS/nixpkgs/pull/519093
github_pr

dnsmasq: 2.92 -> 2.92rel2

Fix merged in NixOS/nixpkgs PR #519082 on 2026-05-11 — awaiting tagged release

https://github.com/NixOS/nixpkgs/pull/519082

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntudnsmasq-utils (2.91-1ubuntu0.2) @ questing2026-08-25ubuntu
redhatdnsmasq-0:2.90-7.el10_22026-05-19redhat

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)
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
dnsmasq2.91-r1
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
dnsmasq2.91-r1
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
dnsmasq2.92_p2-r0
Debian:12(1)
PackageVulnerable rangeFixed inDependents
dnsmasq2.89-1, 2.90-1, 2.90-2, 2.90-3, 2.90-4~deb12u12.90-4~deb12u2
Debian:13(1)
PackageVulnerable rangeFixed inDependents
dnsmasq2.91-12.91-1+deb13u1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
dnsmasq2.91-1 ... 2.92~rc3-1 (9 versions)2.92-5

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

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 9× in last 7d / 84× 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 282 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-5172?
CVE-2026-5172 is a high vulnerability published on May 11, 2026. A buffer overflow in dnsmasq’s extractaddresses() function allows an attacker to trigger a heap out-of-bounds read and crash by exploiting a malformed DNS response, enabling extractname() to advance the pointer past the record’s end.
When was CVE-2026-5172 disclosed?
CVE-2026-5172 was first published in the National Vulnerability Database on May 11, 2026, with the most recent update on September 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-5172 actively exploited?
CVE-2026-5172 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.2% of all scored CVEs.
What is the CVSS score of CVE-2026-5172?
CVE-2026-5172 has a CVSS v3.1 base score of 7.3 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-5172?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-5172, 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-2026-5172

Explore →

Is Your Infrastructure Affected by CVE-2026-5172?

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