{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44193 exists.","fix":"No fix has been published for CVE-2026-44193 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-44193 is a critical command injection vulnerability in opnsense core, published on 13 May 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-44193 and fix it if it is affected.\n\nWhat it is: CVE-2026-44193 is a critical command injection vulnerability in opnsense core, published on 13 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44193 exists.\n\nAffected product: opnsense core. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-44193/ (Markdown: https://insights.sbomify.com/CVE-2026-44193/index.md)","id":"CVE-2026-44193","markdown":"https://insights.sbomify.com/CVE-2026-44193/index.md","name":"CVE-2026-44193","record":{"aliases":["GHSA-xxp9-93cr-x54p"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"OPNsense firewall","requires_auth":"high_privilege","summary":"Attackers can execute arbitrary code on OPNsense firewalls via the XMLRPC restore_config_section method due to insufficient input sanitization.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"opnsense","vendor":"opnsense"}],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-88","name":"Improper Neutralization of Argument Delimiters in a Command"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"OPNsense: RCE via XMLRPC endpoint using `opnsense.restore_config_section` method","id":"CVE-2026-44193","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"OPNsense: RCE on user managment","id":"CVE-2026-44194"},"packages":[],"prev":{"headline":"Ansible-lightspeed: ansible lightspeed mcp server: remote code execution and data exfiltration via path traversal","id":"CVE-2026-44192"},"products":["core"],"published":"2026-05-13","related":[{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2023-27152","kev_date_added":null,"published":"2023-10-23"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2023-39001","kev_date_added":null,"published":"2023-08-09"},{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2023-39004","kev_date_added":null,"published":"2023-08-09"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2023-39008","kev_date_added":null,"published":"2023-08-09"},{"cvss_score":9.6,"headline":"Cross-site scripting in n/a","id":"CVE-2023-39007","kev_date_added":null,"published":"2023-08-09"},{"cvss_score":9.1,"headline":"OPNsense: RCE on user managment","id":"CVE-2026-44194","kev_date_added":null,"published":"2026-05-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-05-16","vendors":["opnsense"]},"summary":"Attackers can execute arbitrary code on OPNsense firewalls via the XMLRPC restore_config_section method due to insufficient input sanitization.","url":"https://insights.sbomify.com/CVE-2026-44193/"}