CVE-2026-58390Public exploitNetwork attack vector

Root execution via quote-unsafe VPN status attributes

Published Oct 15, 2026 · Updated Oct 15, 2026

Stored XSS in OPNsense Core before 26.1.11 allows remote authenticated users to run scripts via OpenVPN status views. OpenVPNClients.js and the connection-status view insert common_name into data-common-name attributes without quote-safe encoding, allowing a double quote to introduce an event handler. Exploitation requires username-as-common-name, RADIUS or LDAP authentication, control over provisioning a valid quoted backend username across a separate identity-administration trust boundary, and administrator interaction with the rendered row; the demonstrated pointer-triggered script reads configuration and obtains root command execution, while local-database usernames reject quotes.

CVSS severity8.0
High
EPSS probability0.48%
Next 30 days · Oct 19, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Get started

Summary

What happened

Stored XSS in OPNsense Core before 26.1.11 allows remote authenticated users to run scripts via OpenVPN status views. OpenVPNClients.js and the connection-status view insert common_name into data-common-name attributes without quote-safe encoding, allowing a double quote to introduce an event handler. Exploitation requires username-as-common-name, RADIUS or LDAP authentication, control over provisioning a valid quoted backend username across a separate identity-administration trust boundary, and administrator interaction with the rendered row; the demonstrated pointer-triggered script reads configuration and obtains root command execution, while local-database usernames reject quotes.

The record

CVE
CVE-2026-58390
Published
Oct 15, 2026
Updated
Oct 15, 2026
Vendor
OPNsense
Product
OPNsense Core
Classifications
CWE-79, T1203
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Oct 15, 2026CVE publishedPublication date reported by the CVE source.
  2. Oct 15, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 26.1.11

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

OPNsense · OPNsense Coreversion=< 26.1.11

Published CVSS scores

8.0OPNsense / GitHub CNACVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Activity data is delayed. The latest report is Sep 28, 2026.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
T1203Exploitation for Client Execution

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Get started to see how Hinoki identifies affected software and validates exploitability in your environment.

Get started