UpSignOn for Windows before 7.19.0 contains a sensitive data exposure vulnerability that allows local attackers to recover the master password and decrypt vault contents by reading a retained backup key from the process memory of UpSignOn.exe, even after the vault has been re-locked. Attackers can extract the backup key from process memory to decrypt the encrypted master password backup stored in v6-vault1.DATA.txt, then use the recovered master password to decrypt the main vault and export all password manager entries in cleartext.
CVE-2026-75135
Score 6.1 from GitHub Security Advisory published 2026-09-02. a secondary CVSS source baseline 6.1; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- 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 computedSeverity61% × 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, 2026UpSignOn < 7.19.0 Sensitive Key Retention in Memory | Advisories | VulnCheck
https://www.vulncheck.com/advisories/upsignon-sensitive-key-retention-in-memoryVendor Advisories for CVE-2026-75135(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 / 34× 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.
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 18:23 UTCEG score recompute
- 2026-09-18 18:23 UTCGHSA enrichment
- 2026-09-17 16:11 UTCEG score recompute
- 2026-09-17 16:11 UTCGHSA enrichment
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 13:59 UTCGHSA enrichment
- 2026-09-15 11:00 UTCGHSA enrichment
- 2026-09-14 08:17 UTCGHSA enrichment
- 2026-09-13 06:05 UTCGHSA enrichment
- 2026-09-12 03:54 UTCEG score recompute
- 2026-09-12 03:54 UTCGHSA enrichment
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 01:42 UTCEG score recompute
- 2026-09-11 01:42 UTCGHSA enrichment
- 2026-09-10 09:35 UTCEPSS rescore
- 2026-09-09 23:30 UTCGHSA enrichment
- 2026-09-08 20:50 UTCGHSA enrichment
- 2026-09-08 07:54 UTCGHSA enrichment
- 2026-09-07 05:43 UTCEG score recompute
- 2026-09-07 05:42 UTCGHSA enrichment
- 2026-09-06 13:48 UTCEPSS rescore
- 2026-09-06 03:31 UTCEG score recompute
- 2026-09-06 03:31 UTCGHSA enrichment
- 2026-09-05 01:18 UTCEG score recompute
Show 9 moreShow fewer
- 2026-09-05 01:17 UTCGHSA enrichment
- 2026-09-05 00:47 UTCEG score recompute
- 2026-09-05 00:47 UTCGHSA enrichment
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-03 22:34 UTCEG score recompute
- 2026-09-03 22:33 UTCGHSA enrichment
- 2026-09-02 20:21 UTCEG score recompute
- 2026-09-02 19:27 UTCEG score recompute
- 2026-09-02 19:25 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-75135?
When was CVE-2026-75135 disclosed?
Is CVE-2026-75135 actively exploited?
What is the CVSS score of CVE-2026-75135?
How do I remediate CVE-2026-75135?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-75135
Is Your Infrastructure Affected by CVE-2026-75135?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.