CVE-2026-61876

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-12. the CNA's CVSS baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:vulncheck, epss, ghsa
Trending — 4 sources updated this weekElevated
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 0

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

LuCI versions fail to properly encode DHCPv6 lease hostnames before rendering in status tables, allowing adjacent network attackers to inject HTML markup. Attackers can send a DHCPv6 Client FQDN containing script tags that execute in the administrator's browser when viewing DHCP lease pages.

CVSS v3
8.8
EG Score
8.8(high)
EPSS
10.0%
KEV
Not listed

Published

July 12, 2026

Last Modified

July 14, 2026

Advisory Details (2)

Auto-updated Jul 12, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

LuCI DHCPv6 Lease Hostname Stored Cross-Site Scripting | Advisories | VulnCheck

https://www.vulncheck.com/advisories/luci-dhcpv6-lease-hostname-stored-cross-site-scripting
github Patch Available🟡 PoC Available

luci-mod-network: luci-mod-status: DHCPv6 lease hostname stored XSS in LuCI status tables · Advisory · openwrt/luci · GitHub

https://github.com/openwrt/luci/security/advisories/GHSA-686p-p8p9-x6fh

Vendor Advisories for CVE-2026-61876(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 18× in last 7d / 18× 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-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 15:05 UTCEG score recompute
  3. 2026-07-15 15:05 UTCGHSA enrichment
  4. 2026-07-15 02:37 UTCEG score recompute
  5. 2026-07-15 02:37 UTCGHSA enrichment
  6. 2026-07-15 02:00 UTCEPSS rescore
  7. 2026-07-15 02:00 UTCEPSS rescore
  8. 2026-07-14 14:06 UTCEG score recompute
  9. 2026-07-14 14:06 UTCGHSA enrichment
  10. 2026-07-14 01:38 UTCEG score recompute
  11. 2026-07-14 01:38 UTCGHSA enrichment
  12. 2026-07-13 22:31 UTCEPSS rescore
  13. 2026-07-13 13:10 UTCEG score recompute
  14. 2026-07-13 13:10 UTCGHSA enrichment
  15. 2026-07-13 00:42 UTCEG score recompute
  16. 2026-07-13 00:41 UTCGHSA enrichment
  17. 2026-07-12 12:13 UTCEG score recompute
  18. 2026-07-12 12:12 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-61876?
CVE-2026-61876 is a high vulnerability published on July 12, 2026. LuCI versions fail to properly encode DHCPv6 lease hostnames before rendering in status tables, allowing adjacent network attackers to inject HTML markup. Attackers can send a DHCPv6 Client FQDN containing script tags that execute in the administrator's browser when viewing DHCP lease pages.
When was CVE-2026-61876 disclosed?
CVE-2026-61876 was first published in the National Vulnerability Database on July 12, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-61876 actively exploited?
CVE-2026-61876 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 10.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-61876?
CVE-2026-61876 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-61876?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-61876, 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

Explore the affected products and dependency analysis for CVE-2026-61876

Explore →

Is Your Infrastructure Affected by CVE-2026-61876?

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

Start Free Scan →Browse All CVEs