CVE-2026-58394

OPNsense, a FreeBSD-based firewall and routing platform, prior to 26.1.11 mishandles privilege values in ACL::hasPrivilege(). A user directly assigned both a component write privilege and user-config-readonly can be treated as lacking the read-only restriction, allowing MVC APIs to persist configuration changes.

OPNsense, a FreeBSD-based firewall and routing platform, prior to 26.1.11 allows carriage-return and line-feed characters in the WebGUI login username field. An attacker with network access to the login page can forge authentication events for another IP, adding it to the sshlockout PF table, or reset their own brute-force counter.

OPNsense is a FreeBSD based firewall and routing platform. Prior to version 26.1.11, the safe-delete path reached through ApiMutableModelControllerBase::delBase() interpolates an unvalidated safe-delete token from the request URL into an XPath expression over config.xml before confirming that the token is a valid identifier. A user holding any one affected module privilege can send a crafted token to one of 21 affected delete endpoints covering Traffic Shaper, DHCP relay, Dnsmasq, Firewall Category, or Kea DHCP, causing the XPath to match configuration data across modules. The resulting error response exposes configuration item names, descriptions, reference paths, and UUIDs and provides an XPath substring-presence oracle, including for modules the user cannot otherwise access. The request does not modify configuration or perform a deletion. This issue is fixed in version 26.1.11.

OPNsense is a FreeBSD based firewall and routing platform. Prior to version 26.1.11, the OpenVPN Client Specific Override common_name field accepts path traversal sequences and openvpn_csc_conf_write() concatenates the value into /var/etc/openvpn-csc/<vpnid>/<common_name> without normalization or a basename check. The affected event handlers are client_connect.php and user_pass_verify.php. An authenticated user with Client Specific Override privileges can store the traversal value, and a matching OpenVPN client-connect or authentication event causes a generated CSO file to be written outside the intended directory. The file content is generated OpenVPN configuration rather than arbitrary bytes, and practical exploitation requires the attacker to cause a matching common name or username to be processed. This issue is fixed in version 26.1.11.

OPNsense is a FreeBSD based firewall and routing platform. Prior to version 26.1.11, the NTP GPS page stores the operator-supplied initcmd value in base64 form, applies legacy_html_escape_form_data() to the encoded string, and then uses base64_decode() to decode the value directly into the GPS initialization-command textarea in src/www/services_ntpd_gps.php. Because decoding occurs after escaping, stored HTML remains unescaped at the output sink. A user with page-services-ntp-gps privilege can store a value that closes the textarea, and script executes in the session of any user who later opens the GPS page. The script can read CSRF material and perform authenticated actions, including actions available to an administrator. This issue is fixed in version 26.1.11.

In OPNsense prior to version 26.1.11, Firewall Rules and NAT views place stored category names and alias descriptions into HTML title attributes without quote-safe encoding. The response layer uses ENT_NOQUOTES, so a double quote survives and closes the attribute, allowing an event-handler attribute to be added to the existing span. A user with Firewall Categories or Firewall Alias Edit privileges can store a malicious value that executes script in the session of an administrator opening the affected Rules or NAT page.

In OPNsense before version 26.1.11, the OpenVPN dashboard widget and connection-status view place a client common_name into data-common-name attributes without quote-safe encoding. With username-as-common-name and RADIUS or LDAP authentication, an attacker can inject an event handler and execute script in an administrator's session. Fixed in version 26.1.11.

In OPNsense before version 26.1.10, the Trust module stores attacker-controlled refid values and interpolates them into XPath expressions, allowing a user with CA Manager or Certificate Manager privileges to recover values from config.xml character by character via a boolean refcount oracle. Fixed in version 26.1.10.

In OPNsense prior to 26.1.11, the Firewall Alias GeoIP importer uses an unvalidated CSV country_code value to construct output filenames, allowing path traversal. A user with Firewall Alias Edit privilege can supply a crafted archive and write attacker-controlled content as root, then leverage cron to execute commands as root.

OPNsense is a FreeBSD based firewall and routing platform. Prior to version 26.1.9 of opnsense/core and version 26.4_20 of BE/opnsense/core, a path traversal vulnerability in the NTP configuration module allows an attacker to overwrite arbitrary files on the system as the root user. By manipulating the GPS or PPS serial port parameter, an attacker with access to the NTP configuration can escape the intended directory and write user-controlled data to any file.