Vulnary
← back to the feed
Critical· 9.6official fix available

CVE-2026-62948

OpenWrt routers running versions earlier than 25.12.5 are vulnerable to a cross‑site scripting flaw. The DHCPv6 client writes unescaped hostnames into a lease file, allowing an attacker to inject malicious HTML into the router’s web interface. The flaw can be exploited by anyone who can send a crafted DHCPv6 request to the device.

publishedJul 15, 2026
last modifiedJul 21, 2026
sourcesNVD
severity · cvss
9.6
critical · how bad it is
exploitation · epss
<1%
28th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Aug 20, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

All OpenWrt installations on embedded routers that are using a firmware version older than 25.12.5. Typical users include home and small‑business router owners.

02

Real-world impact

An attacker could inject arbitrary HTML or JavaScript into the router’s admin page, potentially tricking users into clicking links, downloading malware, or revealing sensitive information. The attack does not require any special privileges on the router.

03

Why this severity

The CVSS score of 9.6 reflects that the vulnerability is exploitable over the network (AV:N), requires low effort (AC:L), no user privileges (PR:N), and needs user interaction (UI:R). It also changes the scope of the affected component (S:C) and has high impact on confidentiality, integrity, and availability (C:H/I:H/A:H).

04

What to do about it

official fix available
recommended steps
  1. 01Upgrade OpenWrt to version 25.12.5 or later.
  2. 02Restart the router to ensure the new firmware is active.

NVD-referenced vendor advisory

05

Timeline

  1. Jul 15, 2026 · 18d ago
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Jul 21, 2026 · 12d ago
    Advisory updated
    The NVD record was last revised.
  3. Jul 21, 2026 · 12d ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Privileges requiredNone
User interactionRequired
ScopeChanged
Confidentiality impactHigh
Integrity impactHigh
Availability impactHigh
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →