VulnerabilityPublished 25 Mar 2026

CVE-2026-33253: SANYO DENKI SANUPS SOFTWARE STANDALONE · Unquoted Search Path or Element

Affects SANYO DENKI SANUPS SOFTWARE STANDALONESource CVE Database V5

Compare

Not known to be exploited · CVSS 6.7 Medium.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.0 base score

6.7Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Attack Vector: Local
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Mar 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
SANYO DENKI CO., LTD.SANUPS SOFTWARE STANDALONE	Affected =Ver.1.0.1 to Ver.1.1.4	Fixed in–
SANYO DENKI CO., LTD.SANUPS SOFTWARE	Affected =Ver.2.0.0 to Ver.2.0.2 =Ver.1.0.0 to Ver.1.1.4	Fixed in–

AI-suggested

Restrict write permissions on the root directory of the system drive (e.g., C:\) to only trusted administrators and system processes to prevent unauthorized code placement.
Audit and harden file system permissions regularly to ensure no users or processes have unnecessary write access to critical system directories.
Monitor Windows service registrations for unquoted paths and correct them by quoting the executable paths properly to prevent exploitation.
If possible, upgrade SANUPS SOFTWARE to a version that addresses this vulnerability once a patch is released by SANYO DENKI.
Employ application whitelisting to prevent unauthorized executables from running, especially in system directories.
Use endpoint detection and response (EDR) tools to detect suspicious activity related to service creation or modification.
Implement strict local user privilege management to minimize the number of users with write access to sensitive directories.
Conduct regular security assessments and penetration testing focused on privilege escalation vectors within the environment.
Isolate critical systems running SANUPS SOFTWARE from general user environments to reduce risk of local exploitation.
Maintain up-to-date backups and incident response plans to quickly recover from potential compromises.

Description

SANUPS SOFTWARE provided by SANYO DENKI CO., LTD.registers Windows services with unquoted file paths. A user with the write permission on the root directory of the system drive may execute arbitrary code with SYSTEM privilege.

Impact

The exploitation of CVE-2026-33253 can lead to complete system compromise as the attacker gains SYSTEM-level privileges, the highest level of access on Windows systems. This allows the attacker to execute arbitrary code, potentially installing persistent malware, stealing sensitive data, disrupting services, or pivoting to other systems within the network. The requirement for write access to the root directory limits the attack surface to scenarios where local privilege escalation or misconfigurations exist, but in such cases, the impact is severe. Organizations relying on SANUPS SOFTWARE for critical power management may face operational disruptions, data breaches, or sabotage of industrial control systems. The vulnerability undermines system integrity and availability, and could be leveraged in targeted attacks against industrial or infrastructure environments where SANYO DENKI products are prevalent. Although no exploits are currently known in the wild, the medium CVSS score and high impact potential warrant proactive mitigation to prevent future exploitation.

References

Community reviews

Loading reviews…