OPNsense up to 26.1.6 XMLRPC opnsense.restore_config_section argument injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in OPNsense up to 26.1.6. It has been classified as critical. Impacted is the function opnsense.restore_config_section of the component XMLRPC. Performing a manipulation results in argument injection.
This vulnerability was named CVE-2026-44193. The attack may be initiated remotely. There is no available exploit.
Upgrading the affected component is recommended.
Details
A vulnerability classified as critical has been found in OPNsense up to 26.1.6. This affects the function opnsense.restore_config_section of the component XMLRPC. The manipulation with an unknown input leads to a argument injection vulnerability. CWE is classifying the issue as CWE-88. The product constructs a string for a command to be executed by a separate component
in another control sphere, but it does not properly delimit the
intended arguments, options, or switches within that command string. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
OPNsense is a FreeBSD based firewall and routing platform. Prior to 26.1.7, the XMLRPC method opnsense.restore_config_section fails to sanitize user supplied input leading to Remote Code Execution. This vulnerability is fixed in 26.1.7.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-44193 since 05/05/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Additional levels of successful authentication are necessary for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059 for this issue.
Upgrading to version 26.1.7 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2026-1344). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Affected
- Open Source OPNsense
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.1VulDB Meta Temp Score: 8.0
VulDB Base Score: 7.2
VulDB Temp Score: 6.9
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 9.1
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Argument injectionCWE: CWE-88 / CWE-74 / CWE-707
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: OPNsense 26.1.7
Timeline
05/05/2026 CVE reserved05/14/2026 Advisory disclosed
05/14/2026 VulDB entry created
05/14/2026 VulDB entry last update
Sources
Advisory: GHSA-xxp9-93cr-x54pStatus: Confirmed
CVE: CVE-2026-44193 (🔒)
GCVE (CVE): GCVE-0-2026-44193
GCVE (VulDB): GCVE-100-363753
CERT Bund: WID-SEC-2026-1344 - OPNsense: Mehrere Schwachstellen
Entry
Created: 05/14/2026 05:45Updated: 05/14/2026 20:31
Changes: 05/14/2026 05:45 (66), 05/14/2026 20:31 (7)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.