CVE-2026-56437

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-08. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Uncontrolled search path element issue exists in Pupsman versions prior to 3.9.0. If a crafted DLL file is placed in the same folder as the affected installer and the installer is executed, arbitrary code may be executed with SYSTEM privilege.

CVSS v3
7.8
EG Score
7.8(high)
EPSS
3.3%
KEV
Not listed

Published

July 8, 2026

Last Modified

July 8, 2026

Advisory Details (2)

Auto-updated Jul 8, 2026
No patch confirmed yet.
generic

Pupsman ｜ 関連ソフトウェア ｜ 無停電電源装置（UPS） | 富士電機

https://www.fujielectric.co.jp/products/power_supply/ups/product_detail/software_pupsman.html
generic

JVN#62347140: Multiple vulnerabilities in the installer for Pupsman

https://jvn.jp/en/jp/JVN62347140/

Vendor Advisories for CVE-2026-56437(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 24× in last 7d / 24× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-12 14:58 UTCEG score recompute
  2. 2026-07-12 14:58 UTCGHSA enrichment
  3. 2026-07-12 01:49 UTCEG score recompute
  4. 2026-07-12 01:49 UTCGHSA enrichment
  5. 2026-07-11 12:40 UTCEG score recompute
  6. 2026-07-11 12:40 UTCGHSA enrichment
  7. 2026-07-11 08:27 UTCEPSS rescore
  8. 2026-07-11 08:27 UTCEPSS rescore
  9. 2026-07-10 23:31 UTCEG score recompute
  10. 2026-07-10 23:31 UTCGHSA enrichment
  11. 2026-07-10 10:21 UTCEG score recompute
  12. 2026-07-10 10:20 UTCGHSA enrichment
  13. 2026-07-09 21:10 UTCEG score recompute
  14. 2026-07-09 21:10 UTCGHSA enrichment
  15. 2026-07-09 19:10 UTCEPSS rescore
  16. 2026-07-09 19:10 UTCEPSS rescore
  17. 2026-07-09 08:01 UTCEG score recompute
  18. 2026-07-09 08:01 UTCGHSA enrichment
  19. 2026-07-08 18:51 UTCEG score recompute
  20. 2026-07-08 18:51 UTCGHSA enrichment
  21. 2026-07-08 15:16 UTCEPSS rescore
  22. 2026-07-08 15:16 UTCEPSS rescore
  23. 2026-07-08 05:42 UTCEG score recompute
  24. 2026-07-08 05:40 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-56437?
CVE-2026-56437 is a high vulnerability published on July 8, 2026. Uncontrolled search path element issue exists in Pupsman versions prior to 3.9.0. If a crafted DLL file is placed in the same folder as the affected installer and the installer is executed, arbitrary code may be executed with SYSTEM privilege.
When was CVE-2026-56437 disclosed?
CVE-2026-56437 was first published in the National Vulnerability Database on July 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56437 actively exploited?
CVE-2026-56437 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56437?
CVE-2026-56437 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-56437?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56437, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-56437

Explore →

Is Your Infrastructure Affected by CVE-2026-56437?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs