Skip to main content

Pupsman CVE-2026-57895

| EUVDEUVD-2026-42166 HIGH
Incorrect Default Permissions (CWE-276)
2026-07-08 jpcert GHSA-36rv-fhqc-2cfg
8.5
CVSS 4.0 · Vendor: jpcert
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain low-privileged local account
  2. Delivery
    Write malicious executable to install folder
  3. Exploit
    SYSTEM service launches planted binary
  4. Execution
    Execute arbitrary code as SYSTEM
  5. Impact
    Full host compromise

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V13 - Configuration Default permission hardening
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

The attacker must already have local, low-privileged access to a Windows host running Pupsman prior to 3.9.0 (PR:L, AV:L) - there is no remote or network path and no user interaction is required (UI:N). The specific enabling condition is the incorrectly permissive default ACL on the Pupsman installation folder that permits a standard user to write files there, combined with a Pupsman service/task that executes binaries from that folder under SYSTEM. Exploitation is limited by the need for an existing local account or code-execution foothold and by any environment where the installation directory permissions have already been hardened or where only administrators can log on locally.

Impact

The vendor-supplied CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:L/UI:N with VC:H/VI:H/VA:H) describes a locally-exploitable, low-complexity flaw that requires the attacker to already hold a low-privileged foothold but grants total system compromise on success - a classic high-value privilege-escalation primitive rather than a remotely wormable bug. No EPSS score, KEV listing, or POC reference is present in the provided data, so exploitation probability cannot be quantified from these sources; the local attack vector inherently limits mass exploitation and favors post-compromise use by an attacker who has already landed on the host. This is a genuine priority on systems where untrusted or standard users share a machine running Pupsman, but lower urgency on single-admin appliances. Note the two references (Fuji Electric product page and the JVN advisory) were provided without descriptive titles, so the exact patched-version confirmation rests on the description's 'prior to 3.9.0' statement.

Exploit ScenarioDerived

A standard (non-admin) user or a piece of malware already running with limited privileges on a Windows host writes a malicious executable into the writable Pupsman installation folder, replacing or adding a binary that the SYSTEM-level service or a scheduled task subsequently launches. On next execution - a reboot, service restart, or timed run - the attacker's code runs as SYSTEM, yielding full host takeover. The low attack complexity (AC:L) means no special timing or race is needed; no public POC is referenced in the provided data.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 08, 2026

Local privilege escalation to SYSTEM in Fuji Electric Pupsman before version 3.9.0 allows a low-privileged local user to drop a malicious executable into the weakly-permissioned installation directory, which is then run with SYSTEM privileges for full arbitrary code execution. Reported through JPCERT/CC (JVN JVN62347140); no public exploit identified and no active exploitation is confirmed at time of analysis. The CVSS 4.0 base score is 8.5 (High), reflecting complete confidentiality, integrity, and availability impact despite the local attack vector.

RemediationAI

Vendor-released patch: upgrade Pupsman to version 3.9.0 or later, which corrects the installation-folder permissions; download and advisory details are on the Fuji Electric page (https://www.fujielectric.co.jp/products/power_supply/ups/product_detail/software_pupsman.html) and JVN (https://jvn.jp/en/jp/JVN62347140/). Where immediate patching is not possible, the direct compensating control is to tighten the ACLs on the Pupsman installation directory so that only Administrators and SYSTEM have write/modify permissions and standard users are restricted to read/execute - this directly removes the attacker's ability to plant a binary, with the trade-off that a future in-place update or repair run by the installer may reset directory permissions and must be re-hardened afterward. Additionally, restrict interactive and local logon on hosts running the Pupsman service to trusted administrators to shrink the pool of potential low-privileged attackers.

Affected VersionsENISA

Pupsman prior to 3.9.0

Affected Packages

euvd pupsman_prior_to no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Pupsman is Fuji Electric's UPS (uninterruptible power supply) monitoring and management software for Windows, typically running a service under the SYSTEM account. The root cause is CWE-276 (Incorrect Default Permissions): the product's installation folder is created with overly permissive ACLs that let non-administrative users write to it. Because a SYSTEM-context service or scheduled task executes binaries from that directory, any executable a standard user plants there inherits SYSTEM privileges. The single affected CPE is cpe:2.3:a:fuji_electric_co.,ltd.:pupsman, confirming this is application-level rather than an OS or protocol flaw.

Know when Pupsman gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (jpcert) PRIMARY 8.5 HIGH
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
vuln.today AI 7.8 HIGH

Local vector and low-privileged foothold required (AV:L, PR:L), no user interaction and low complexity, with full SYSTEM-level C/I/A impact; scope unchanged as the service runs on the same OS.

3.1 AV:L/AC:L/PR:L/UI:N/S:N/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (jpcert).

CVSS VectorVendor: jpcert

Attack Vector
Local
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

1
CVSS changed
Jul 08, 2026 - 06:22 NVD
7.8 (HIGH) 8.5 (HIGH)

DescriptionCVE.org

Incorrect default permissions issue exists in Pupsman versions prior to 3.9.0. An attacker can place a malicious executable in the installation folder, which results in arbitrary code execution with SYSTEM privilege

Executive ViewAI

Why It Matters

Fuji Electric Pupsman versions before 3.9.0 can be compromised by local users to gain complete SYSTEM-level access and full control of operational systems. With no public exploit code currently available and no active exploitation confirmed, organizations have a limited window to implement controls. Any affected system represents a critical insider risk and potential point of failure for operational continuity and system integrity.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) Restrict write permissions on Pupsman installation and execution directories to SYSTEM and administrators only, preventing malicious executable placement; (2) Enforce principle of least privilege-disable unnecessary local logon capabilities for service and user accounts; (3) Implement file integrity monitoring and real-time alerting for any modifications within Pupsman directories; (4) Conduct access reviews for all accounts with local system privileges to identify and remediate excessive permissions.

Threat Intelligence Overview

EPSS Score
0.1%
Top 98% exploitable
Prevalence
Low
niche vendor UPS management utility, industrial/facility deployments only
Social Media
2
Sightings
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

42
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +42
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy