Synced 03 Aug 2026 05:54 UTC Account
← OpenWrt

OpenWrt vulnerabilities: known CVEs & security history

OpenWrt · Operating System · 5 tracked CVEs · 0 actively exploited · updated August 2026 · what is a CVE? →

This is the full list of known vulnerabilities (CVEs) across all OpenWrt release lines — 5 in total. A CVE here doesn't mean your version is affected — check OpenWrt's current status and the safe version to run.

5
known CVEs
0
actively exploited (KEV)
1
critical severity
0
ransomware-linked

Known OpenWrt CVEs

Actively-exploited and most-severe first. Open any CVE for full details.

CVESeverityCVSSEPSSYear
CVE-2026-62948 critical 9.6 0% 2026
CVE-2019-17367 high 8.8 1% 2019
CVE-2026-55490 medium 6.5 1% 2026
CVE-2021-33425 medium 5.4 1% 2021
CVE-2026-62947 medium 4.9 0% 2026

Is my OpenWrt version affected?

The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.

Check your OpenWrt version → · Monitor OpenWrt for new CVEs →

OpenWrt vulnerabilities — frequently asked

How many known vulnerabilities does OpenWrt have?

IsItPatched tracks 5 CVEs for OpenWrt. 1 is critical-severity and 1 high-severity. These span every release line — what matters is whether the version you run is affected.

Does OpenWrt have any actively-exploited vulnerabilities?

None of OpenWrt's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.

What is the most severe OpenWrt vulnerability?

Among tracked issues, CVE-2026-62948 (CRITICAL, CVSS 9.6) ranks highest — a Cross-site scripting (XSS) weakness.

Is OpenWrt safe to use?

It depends on the version. The latest supported OpenWrt release (25.12.5) clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.

CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: OpenWrt security status · OpenWrt end-of-life · actively-exploited CVEs. Always verify against OpenWrt's advisories — see our disclaimer.