dhcpcd through 10.3.2, fixed in commit 708b4a5, contains a memory leak vulnerability in the IPv6 Router Advertisement route information handling that allows an unauthenticated same-link attacker to cause denial of service by sending crafted Router Advertisements. Attackers can repeatedly send Router Advertisements containing Route Information options with a lifetime of zero, triggering unfreed allocations in routeinfo_findalloc() that cause linear memory exhaustion and eventual daemon crash.
CVE-2026-56116
Score 6.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-23. the CNA's CVSS baseline 6.5; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(medium)
- EG Risk
- 29(Track)EG Risk 29/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 computedSeverity65% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 21%
- KEV
- Not listed
Published
June 23, 2026
Last Modified
July 28, 2026
Advisory Details (2)
Auto-updated Jun 23, 2026dhcpcd Memory Leak DoS via IPv6 Router Advertisement Handling | Advisories | VulnCheck
https://www.vulncheck.com/advisories/dhcpcd-memory-leak-dos-via-ipv6-router-advertisement-handlingcommit 708b4a56bae0 (NetworkConfiguration/dhcpcd)
Fix landed in NetworkConfiguration/dhcpcd commit 708b4a56bae0 — awaiting tagged release
https://github.com/NetworkConfiguration/dhcpcd/commit/708b4a56bae080a5b18c2e0c4c6fbe103131a2b0Vendor Advisories for CVE-2026-56116(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(2 across 2 ecosystems)
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| dhcpcd | 1:10.1.0-11, 1:10.1.0-11+deb13u1, 1:10.1.0-11+deb13u2 | 1:10.1.0-11+deb13u3 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| dhcpcd | 1:10.1.0-11 ... 1:10.3.2-4~bpo13+1 (37 versions) | 1:10.3.2-4 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 57× 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 211 total refreshes for this CVE.
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-10 09:35 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-04 05:07 UTCEPSS rescore
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-08-30 20:26 UTCEG score recompute
- 2026-08-30 20:26 UTCVendor advisory
- 2026-08-30 20:26 UTCGHSA enrichment
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 13:54 UTCEG score recompute
- 2026-08-24 13:54 UTCVendor advisory
- 2026-08-24 13:54 UTCGHSA enrichment
- 2026-08-23 13:28 UTCVendor advisory
- 2026-08-23 13:28 UTCGHSA enrichment
- 2026-08-22 13:49 UTCEG score recompute
- 2026-08-22 13:49 UTCVendor advisory
Show 75 moreShow fewer
- 2026-08-22 13:49 UTCGHSA enrichment
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 07:19 UTCEG score recompute
- 2026-08-21 07:19 UTCVendor advisory
- 2026-08-21 07:19 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 07:46 UTCEG score recompute
- 2026-08-20 07:46 UTCVendor advisory
- 2026-08-20 07:46 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 04:49 UTCEG score recompute
- 2026-08-19 04:49 UTCVendor advisory
- 2026-08-19 04:49 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 20:18 UTCEG score recompute
- 2026-08-16 20:18 UTCVendor advisory
- 2026-08-16 20:18 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 20:50 UTCEG score recompute
- 2026-08-15 20:50 UTCVendor advisory
- 2026-08-15 20:50 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 21:12 UTCEG score recompute
- 2026-08-14 21:12 UTCVendor advisory
- 2026-08-14 21:12 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 21:44 UTCVendor advisory
- 2026-08-13 21:44 UTCGHSA enrichment
- 2026-08-12 22:17 UTCEG score recompute
- 2026-08-12 22:17 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-11 22:49 UTCEG score recompute
- 2026-08-11 22:49 UTCVendor advisory
- 2026-08-11 22:49 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 23:22 UTCGHSA enrichment
- 2026-08-09 23:54 UTCEG score recompute
- 2026-08-09 23:54 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 00:27 UTCEG score recompute
- 2026-08-09 00:27 UTCVendor advisory
- 2026-08-09 00:27 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 00:59 UTCEG score recompute
- 2026-08-08 00:59 UTCVendor advisory
- 2026-08-08 00:59 UTCGHSA enrichment
- 2026-08-07 01:31 UTCEG score recompute
- 2026-08-07 01:31 UTCVendor advisory
- 2026-08-07 01:31 UTCGHSA enrichment
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-06 02:04 UTCEG score recompute
- 2026-08-06 02:04 UTCVendor advisory
- 2026-08-06 02:04 UTCGHSA enrichment
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 02:36 UTCEG score recompute
- 2026-08-05 02:36 UTCVendor advisory
- 2026-08-05 02:36 UTCGHSA enrichment
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:39 UTCEPSS rescore
- 2026-08-04 02:51 UTCEG score recompute
- 2026-08-04 02:51 UTCVendor advisory
- 2026-08-04 02:51 UTCGHSA enrichment
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-03 03:14 UTCVendor advisory
- 2026-08-03 03:14 UTCGHSA enrichment
- 2026-08-02 03:45 UTCEG score recompute
- 2026-08-02 03:45 UTCVendor advisory
- 2026-08-02 03:45 UTCGHSA enrichment
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 04:17 UTCEG score recompute
- 2026-08-01 04:17 UTCVendor advisory
- 2026-08-01 04:16 UTCGHSA enrichment
- 2026-08-01 04:16 UTCEPSS rescore
Frequently asked(5)
What is CVE-2026-56116?
When was CVE-2026-56116 disclosed?
Is CVE-2026-56116 actively exploited?
What is the CVSS score of CVE-2026-56116?
How do I remediate CVE-2026-56116?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-56116
Is Your Infrastructure Affected by CVE-2026-56116?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.