Servers and applications
CVE-2026-58393
OpenVPN Client Specific Override common_name allows path traversal in generated CSO files
- Severity
- Medium 5.9
- Published
- 1 Jul 2026
- Last changed
- 15 Oct 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 1, 26.1.11
- Exploit chance
- 0.4% in the next 30 daysHigher than 38% of CVEs. EPSS by FIRST, 19 Nov 2026
- Weakness
- Path traversal (CWE-22)
- Attack
- Over the network · Only under certain conditions · Needs a user account · No user action needed
- Attacker can
- Change data · Slow it down
- CVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:L- Also known as
- GHSA-2m9v-p7r9-gfcw
- Sources
- CVE Program, Project advisories (GitHub)
Description
An authenticated OPNsense Web UI/API user with OpenVPN Client Specific Override privileges can store path traversal sequences in the CSO common_name field. When the OpenVPN CSO writer materializes a matching override, the value is concatenated into /var/etc/openvpn-csc// without normalization or a basename check, allowing creation of a generated CSO file outside the intended OpenVPN CSO directory.
This was dynamically verified on a local OPNsense VM. A CSO common_name of ../../../../tmp/poc_openvpn_cso_common_name.txt caused openvpn_csc_conf_write() to write /tmp/poc_openvpn_cso_common_name.txt. Temporary OpenVPN objects and the marker file were removed afterwards.
The OpenVPN model defines the Client Specific Override common name as a plain text field:
The CSO API stores this object through generic model helpers:
The OpenVPN event paths look up a matching CSO and call openvpn_csc_conf_write():
The vulnerable filename construction is in openvpn_csc_conf_write():
Affected software
| Software | Affected versions |
|---|---|
OPNsenseServers and applications · cna:opnsense|core |
|
OPNsenseServers and applications · github:opnsense/core |
|
About OPNsense
open-source firewall
- GitHub stars
- 4,802GitHub, 15 Nov 2026
- Forks
- 1,029GitHub, 15 Nov 2026
- License
- 2-clause BSD LicenseWikidata
- Written in
- PHP, CWikidata
- First released
- 2 Jan 2015Wikidata
- First published on GitHub
- 13 Dec 2014GitHub
Release lines
| Release | Latest | Security fixes |
|---|---|---|
| 26.7 'Xenial Xenops' | 26.7.9 | Yes |
| 26.1 'Witty Woodpecker' | 26.1.11 | Ended 15 Jul 2026 |
| 25.7 'Visionary Viper' | 25.7.11 | Ended 28 Jan 2026 |
| 25.1 'Ultimate Unicorn' | 25.1.12 | Ended 23 Jul 2025 |
| 24.7 'Thriving Tiger' | 24.7.12 | Ended 28 Jan 2025 |
| 24.1 'Savvy Shark' | 24.1.10 | Ended 25 Jul 2024 |
From endoflife.date.
Vulnerabilities in OPNsense
- In our list
- 71
- Published in the last 12 months
- 51
- Critical, last 12 months
- 5
- High, last 12 months
- 13
- Known exploited
- 0
- GHSA-f35q-c34m-pfw3Unquoted PPP password in mpd_*.conf allows root command execution (incomplete fix of CVE-2026-57154)High 7.2 11 Nov 2026
- GHSA-2f7g-25f3-55v7Source-restricted page-all group satisfies Monit full-admin check outside its allowed networkMedium 11 Nov 2026
- GHSA-2w8j-hpp2-8rfjLimited Status users can delete crash evidence through dismiss_statusMedium 11 Nov 2026
- GHSA-r23v-737v-6r5hCaptive Portal template ZIP expansion exhausts WebGUI and backend memoryMedium 11 Nov 2026
- CVE-2026-119560OPNsense core through 26.7.8 NTP Configuration Injection via GPS and PPS Fudge FieldsMedium 6.0 30 Oct 2026
- CVE-2026-119425OPNsense 26.1.6 through 26.7.7 Captive Portal Session Takeover via Forged ARPMedium 5.3 30 Oct 2026
References
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-58393
- GitHub Advisory Database https://github.com/advisories/GHSA-2m9v-p7r9-gfcw
- github.com https://github.com/opnsense/core/security/advisories/GHSA-2m9v-p7r9-gfcw