CVE-2026-58000

HIGHPre-NVD 8.88.8
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-29. a secondary CVSS source baseline 8.8; sources differ by 0.0.

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

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

luci-proto-openvpn through 0.11.1, fixed in commit e4ff45e, contains a command injection vulnerability in the generateKey ubus method where the cl_meta parameter is interpolated into a shell command without proper escaping or quoting. An authenticated LuCI user with OpenVPN protocol configuration access can inject arbitrary shell metacharacters into cl_meta to execute commands as root via the popen function.

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

Published

June 29, 2026

Last Modified

June 30, 2026

Advisory Details (3)

Auto-updated Jun 29, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
generic

luci-proto-openvpn - Command Injection via cl_meta Parameter in generateKey | Advisories | VulnCheck

https://www.vulncheck.com/advisories/luci-proto-openvpn-command-injection-via-cl-meta-parameter-in-generatekey
github Patch Available🟡 PoC Available

Command injection as root in luci-proto-openvpn generateKey (cl_meta field) · Advisory · openwrt/luci · GitHub

https://github.com/openwrt/luci/security/advisories/GHSA-pm9w-522m-8rrh
github_commit

commit e4ff45ecbc6a (openwrt/luci)

Fix landed in openwrt/luci commit e4ff45ecbc6a — awaiting tagged release

https://github.com/openwrt/luci/commit/e4ff45ecbc6ad212951815c8c99b2749fbd7de6b

Vendor Advisories for CVE-2026-58000(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 34× in last 7d / 38× 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-06 20:57 UTCEG score recompute
  2. 2026-07-06 20:57 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 07:49 UTCEG score recompute
  6. 2026-07-06 07:49 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 18:39 UTCEG score recompute
  10. 2026-07-05 18:39 UTCGHSA enrichment
  11. 2026-07-05 05:36 UTCEG score recompute
  12. 2026-07-05 05:35 UTCGHSA enrichment
  13. 2026-07-05 02:31 UTCEPSS rescore
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-04 16:30 UTCEG score recompute
  16. 2026-07-04 16:30 UTCGHSA enrichment
  17. 2026-07-04 06:31 UTCEPSS rescore
  18. 2026-07-04 06:31 UTCEPSS rescore
  19. 2026-07-04 03:23 UTCEG score recompute
  20. 2026-07-04 03:23 UTCGHSA enrichment
  21. 2026-07-03 14:20 UTCEG score recompute
  22. 2026-07-03 14:20 UTCGHSA enrichment
  23. 2026-07-03 01:17 UTCEG score recompute
  24. 2026-07-03 01:17 UTCGHSA enrichment
  25. 2026-07-02 12:13 UTCEG score recompute
Show 13 more
  1. 2026-07-02 12:13 UTCGHSA enrichment
  2. 2026-07-01 23:08 UTCEG score recompute
  3. 2026-07-01 23:08 UTCGHSA enrichment
  4. 2026-07-01 15:07 UTCEPSS rescore
  5. 2026-07-01 10:05 UTCEG score recompute
  6. 2026-07-01 10:05 UTCGHSA enrichment
  7. 2026-06-30 23:22 UTCEPSS rescore
  8. 2026-06-30 21:02 UTCEG score recompute
  9. 2026-06-30 21:01 UTCGHSA enrichment
  10. 2026-06-30 07:57 UTCEG score recompute
  11. 2026-06-30 07:57 UTCGHSA enrichment
  12. 2026-06-29 18:54 UTCEG score recompute
  13. 2026-06-29 18:53 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-58000?
CVE-2026-58000 is a high vulnerability published on June 29, 2026. luci-proto-openvpn through 0.11.1, fixed in commit e4ff45e, contains a command injection vulnerability in the generateKey ubus method where the clmeta parameter is interpolated into a shell command without proper escaping or quoting. An authenticated LuCI user with OpenVPN protocol configuration…
When was CVE-2026-58000 disclosed?
CVE-2026-58000 was first published in the National Vulnerability Database on June 29, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-58000 actively exploited?
CVE-2026-58000 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 69.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-58000?
CVE-2026-58000 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-58000?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58000, 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-58000

Explore →

Is Your Infrastructure Affected by CVE-2026-58000?

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