CVE-2026-75137

MEDIUMPre-NVD 6.16.1—
EchelonGraph scoreHIGH confidence

Score 6.1 from GitHub Security Advisory published 2026-09-02. a secondary CVSS source baseline 6.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
6.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.1Exploit: None knownExposed: 0

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

UpSignOn for Windows before 7.19.0 contains a sensitive data exposure vulnerability that allows local attackers to recover cleartext vault data from process memory even after the application has been locked. Attackers can use the PROCESS_VM_READ permission to read the memory space of UpSignOn.exe and extract sensitive fields including entry names, URLs, usernames, passwords, TOTP secrets, and notes.

CVSS v3
6.1
EG Score
6.1(high)
EG Risk
27(Track)
EG Risk 27/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity61% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
0%
KEV
Not listed

Published

September 2, 2026

Last Modified

September 8, 2026

Advisory Details (2)

Auto-updated Sep 2, 2026
No patch confirmed yet.
generic

UpSignOn < 7.19.0 Sensitive Data Exposure in Process Memory after Lock | Advisories | VulnCheck

https://www.vulncheck.com/advisories/upsignon-sensitive-data-exposure-in-process-memory-after-lock
generic

Release notes

https://upsignon.eu/en/resources/release-notes/app#7.19.0

Vendor Advisories for CVE-2026-75137(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 10× in last 7d / 35× 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-09-19 08:54 UTCGHSA enrichment
  2. 2026-09-18 07:47 UTCEG score recompute
  3. 2026-09-18 07:47 UTCGHSA enrichment
  4. 2026-09-17 06:46 UTCEG score recompute
  5. 2026-09-17 06:46 UTCGHSA enrichment
  6. 2026-09-16 14:08 UTCEPSS rescore
  7. 2026-09-16 05:44 UTCGHSA enrichment
  8. 2026-09-15 04:42 UTCGHSA enrichment
  9. 2026-09-14 03:37 UTCGHSA enrichment
  10. 2026-09-13 02:36 UTCGHSA enrichment
  11. 2026-09-12 01:34 UTCEG score recompute
  12. 2026-09-12 01:34 UTCGHSA enrichment
  13. 2026-09-11 14:53 UTCEPSS rescore
  14. 2026-09-11 00:31 UTCEG score recompute
  15. 2026-09-11 00:31 UTCGHSA enrichment
  16. 2026-09-10 09:35 UTCEPSS rescore
  17. 2026-09-09 23:30 UTCEG score recompute
  18. 2026-09-09 23:30 UTCGHSA enrichment
  19. 2026-09-08 22:01 UTCEPSS rescore
  20. 2026-09-08 20:50 UTCGHSA enrichment
  21. 2026-09-07 19:40 UTCGHSA enrichment
  22. 2026-09-06 18:39 UTCEG score recompute
  23. 2026-09-06 18:39 UTCGHSA enrichment
  24. 2026-09-06 13:48 UTCEPSS rescore
  25. 2026-09-05 17:36 UTCGHSA enrichment
Show 10 more
  1. 2026-09-04 16:33 UTCEG score recompute
  2. 2026-09-04 16:33 UTCGHSA enrichment
  3. 2026-09-04 05:07 UTCEPSS rescore
  4. 2026-09-03 15:31 UTCEG score recompute
  5. 2026-09-03 15:31 UTCGHSA enrichment
  6. 2026-09-03 14:35 UTCEG score recompute
  7. 2026-09-03 14:35 UTCGHSA enrichment
  8. 2026-09-02 20:21 UTCEG score recompute
  9. 2026-09-02 19:26 UTCEG score recompute
  10. 2026-09-02 19:25 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-75137?
CVE-2026-75137 is a medium vulnerability published on September 2, 2026. UpSignOn for Windows before 7.19.0 contains a sensitive data exposure vulnerability that allows local attackers to recover cleartext vault data from process memory even after the application has been locked. Attackers can use the PROCESSVMREAD permission to read the memory space of UpSignOn.exe and…
When was CVE-2026-75137 disclosed?
CVE-2026-75137 was first published in the National Vulnerability Database on September 2, 2026, with the most recent update on September 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-75137 actively exploited?
CVE-2026-75137 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 99.9% of all scored CVEs.
What is the CVSS score of CVE-2026-75137?
CVE-2026-75137 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-75137?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-75137, 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-75137

Explore →

Is Your Infrastructure Affected by CVE-2026-75137?

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

Start Free Scan →Browse All CVEs