A flaw was found in dnsmasq. A remote attacker could exploit an out-of-bounds write vulnerability by sending a specially crafted BOOTREPLY (Bootstrap Protocol Reply) packet to a dnsmasq server configured with the --dhcp-split-relay option. This can lead to memory corruption, causing the dnsmasq daemon to crash and resulting in a denial of service (DoS).
CVE-2026-6507
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-04-17. NVD baseline CVSS 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 49(Track)EG Risk 49/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 computedSeverity75% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 40%
- KEV
- Not listed
Published
April 17, 2026
Last Modified
September 1, 2026
Advisory Details (2)
Auto-updated Jun 11, 20262459181 – (CVE-2026-6507) CVE-2026-6507 dnsmasq: dnsmasq: Denial of Service due to out-of-bounds write in DHCP BOOTREPLY processing
https://bugzilla.redhat.com/show_bug.cgi?id=2459181Vendor Advisories for CVE-2026-6507(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | dnsmasq-utils (2.92-1ubuntu0.3) @ resolute | 2026-08-26 | ubuntu |
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
(1 across 1 ecosystem)
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| dnsmasq | 2.91-1 ... 2.92~rc3-1 (8 versions) | 2.92-4 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
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 4× in last 7d / 36× 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 229 total refreshes for this CVE.
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-12 15:02 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-05 15:31 UTCEPSS rescore
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 12:27 UTCGHSA enrichment
- 2026-09-01 11:50 UTCEG score recompute
- 2026-09-01 11:50 UTCGHSA enrichment
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-08-31 17:24 UTCGHSA enrichment
- 2026-08-31 16:58 UTCEG score recompute
- 2026-08-31 16:57 UTCGHSA enrichment
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-26 18:25 UTCVendor advisory
- 2026-08-26 18:25 UTCGHSA enrichment
- 2026-08-26 17:45 UTCEG score recompute
- 2026-08-26 17:45 UTCVendor advisory
- 2026-08-26 17:45 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 06:32 UTCEG score recompute
- 2026-08-16 06:32 UTCVendor advisory
- 2026-08-16 06:32 UTCGHSA enrichment
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-15 01:31 UTCEPSS rescore
- 2026-08-14 18:08 UTCVendor advisory
- 2026-08-14 18:08 UTCGHSA enrichment
- 2026-08-14 04:38 UTCEG score recompute
- 2026-08-14 04:38 UTCVendor advisory
- 2026-08-14 04:38 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 08:53 UTCVendor advisory
- 2026-08-13 08:53 UTCGHSA enrichment
- 2026-08-12 18:49 UTCEG score recompute
- 2026-08-12 18:49 UTCVendor advisory
- 2026-08-12 18:49 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-11 16:58 UTCEG score recompute
- 2026-08-11 16:58 UTCVendor advisory
- 2026-08-11 16:58 UTCGHSA enrichment
- 2026-08-11 02:34 UTCEG score recompute
- 2026-08-11 02:34 UTCVendor advisory
- 2026-08-11 02:34 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 05:44 UTCVendor advisory
- 2026-08-10 05:44 UTCGHSA enrichment
- 2026-08-09 16:49 UTCEG score recompute
- 2026-08-09 16:49 UTCVendor advisory
- 2026-08-09 16:49 UTCGHSA enrichment
- 2026-08-09 13:47 UTCEPSS rescore
- 2026-08-09 03:54 UTCEG score recompute
- 2026-08-09 03:54 UTCVendor advisory
- 2026-08-09 03:54 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 02:15 UTCEG score recompute
- 2026-08-08 02:15 UTCVendor advisory
- 2026-08-08 02:15 UTCGHSA enrichment
- 2026-08-07 13:20 UTCEG score recompute
- 2026-08-07 13:20 UTCVendor advisory
- 2026-08-07 13:20 UTCGHSA enrichment
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-06 12:15 UTCVendor advisory
- 2026-08-06 12:15 UTCGHSA enrichment
- 2026-08-05 23:19 UTCEG score recompute
- 2026-08-05 23:19 UTCVendor advisory
- 2026-08-05 23:19 UTCGHSA enrichment
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:39 UTCEPSS rescore
- 2026-08-03 21:31 UTCEG score recompute
- 2026-08-03 21:31 UTCVendor advisory
- 2026-08-03 21:31 UTCGHSA enrichment
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-03 01:59 UTCVendor advisory
- 2026-08-03 01:59 UTCGHSA enrichment
- 2026-08-02 13:04 UTCEG score recompute
- 2026-08-02 13:04 UTCVendor advisory
- 2026-08-02 13:04 UTCGHSA enrichment
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-28 15:37 UTCEPSS rescore
Related CVEs(same vendor + same CWE)
Same vendor
10 shownubuntu
- CVE-2004-0989EG 10.0EPSS p97HIGH
- CVE-2004-0990EG 10.0EPSS p98HIGH
- CVE-2004-1010EG 10.0EPSS p95HIGH
- CVE-2004-0941EG 10.0EPSS p96HIGH
- CVE-2004-0981EG 10.0EPSS p93HIGH
- CVE-2004-0882EG 10.0EPSS p96HIGH
- CVE-2004-0888EG 10.0EPSS p95HIGH
- CVE-2004-1012EG 10.0EPSS p93HIGH
- CVE-2004-1013EG 10.0EPSS p93HIGH
- CVE-2004-1018EG 10.0EPSS p97HIGH
Same CWE
10 shownCWE-787
Frequently asked(5)
What is CVE-2026-6507?
When was CVE-2026-6507 disclosed?
Is CVE-2026-6507 actively exploited?
What is the CVSS score of CVE-2026-6507?
How do I remediate CVE-2026-6507?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-6507
Is Your Infrastructure Affected by CVE-2026-6507?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.