CVE-2026-58390

HIGHPre-NVD 8.08.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (48th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-102136 (ENISA EUVD)Source: ENISA EUVD

8.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 8.0Exploit: No code on recordExposed services: Not assessed

The CVE record names the fixed release — apply it.

OPNsense is a FreeBSD based firewall and routing platform. Prior to version 26.1.11, the OpenVPN connection-status dashboard widget in src/opnsense/www/js/widgets/OpenVPNClients.js and the connection-status view place a client common_name into data-common-name attributes without quote-safe encoding. Exploitation requires an OpenVPN server configured with username-as-common-name and RADIUS or LDAP authentication, plus the ability to provision or self-register a valid backend username containing a double quote; deployments where the same administrator controls both the identity backend and firewall do not cross a separate trust boundary. An authenticated client using that username can close the attribute and add an event handler, while the local user database is not affected because its username validator rejects quotes. Script executes in an administrator's session when the administrator opens the dashboard or connection-status page and the injected event is triggered; the demonstrated payload used pointer movement over the client row rather than unconditional page-load execution. The advisory demonstrates that the script can read config.xml, invoke privileged APIs, reset the root password, and obtain root command execution. This issue is fixed in version 26.1.11.

CVSS v3
8.0
EG Score
8.0HIGHmedium confidence
EG Risk
52
EG Risk 52/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity80% × 45%
Impact severity (EG Severity): CVSS 8.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
48th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.0): severity, escalated by confirmed exploitation. This CVE's 8.0 is its impact severity (EG Severity), not escalated.

EG Severity
8.0 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 15, 2026

Last Modified

October 20, 2026

Advisory Details (3)

Auto-updated Oct 15, 2026
🔬 Proof of concept available. Fix named in the CVE record. Sources: github, github_commit.
GitHub commit

commit e7b2ac8093f8 (opnsense/core)

Fix landed in opnsense/core commit e7b2ac8093f8 — awaiting tagged release

https://github.com/opnsense/core/commit/e7b2ac8093f804bef8eb88dfa9a0d99fad00c12b
GitHub commit

commit 11180daf5798 (opnsense/core)

Fix landed in opnsense/core commit 11180daf5798 — awaiting tagged release

https://github.com/opnsense/core/commit/11180daf579879d84d91a7fbea7a59320bc80868
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Stored XSS to root RCE via OpenVPN client common_name in status views · Advisory · opnsense/core · GitHub

https://github.com/opnsense/core/security/advisories/GHSA-26cj-h9rj-g5pf

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 23× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  2. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  3. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  4. 2026-10-27 18:43 UTCEG score recompute
  5. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  6. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  7. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  8. 2026-10-25 14:16 UTCEG score recompute
  9. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  10. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  11. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  12. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  13. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  14. 2026-10-20 03:26 UTCEG score recompute
  15. 2026-10-20 02:58 UTCEG score recompute
  16. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  17. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  18. 2026-10-18 03:28 UTCEG score recompute
  19. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  20. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  21. 2026-10-15 16:32 UTCEG score recompute
  22. 2026-10-15 15:38 UTCEG score recomputeFirst assessed: 8.0 HIGH
  23. 2026-10-15 15:37 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-58390?
CVE-2026-58390 is a high-severity vulnerability; its CVE record was published on October 15, 2026. OPNsense is a FreeBSD based firewall and routing platform. Prior to version 26.1.11, the OpenVPN connection-status dashboard widget in src/opnsense/www/js/widgets/OpenVPNClients.js and the connection-status view place a client common_name into data-common-name attributes without quote-safe…
When was the CVE record for CVE-2026-58390 published?
The CVE record for CVE-2026-58390 was published on October 15, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 20, 2026; the record at its source may have been updated since.
Is CVE-2026-58390 actively exploited?
CVE-2026-58390 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-58390?
CVE-2026-58390 has a CVSS base score of 8.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-58390?
The CVE record for CVE-2026-58390 names the fix: "This issue is fixed in version 26.1.11."

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-58390?

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

Book a Demo →Browse All CVEs