CVE-2026-5965: NewSoft NewSoftOA · OS Command Injection
Affects NewSoft NewSoftOASource CVE Database V5
Not known to be exploited · CVSS 9.3 Critical : upgrade to 10.1.8.3 as a priority.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 1.6% chance of exploitation in 30 days – higher than 76% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 10.1.8.3
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 21 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade NewSoft NewSoftOA to 10.1.8.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| NewSoftNewSoftOA | Affected
| Fixed in
|
AI-suggested
Until a fix is provided, restricting local access to trusted users and employing host-based intrusion prevention may reduce risk. Avoid exposing vulnerable instances to untrusted local users.
Description
CVE-2026-5965 is a critical OS Command Injection vulnerability in NewSoftOA by NewSoft. It allows unauthenticated local attackers to inject and execute arbitrary operating system commands on the server. The vulnerability is due to improper neutralization of special elements used in OS commands (CWE-78). The vulnerability has a high CVSS 4.0 score of 9.3, indicating critical severity. There are no known exploits in the wild at this time. The affected version is listed as '0', which may indicate an initial or unspecified version. Since this is not a cloud service, remediation depends on vendor patching or user mitigation.