Quick answers
- Is CVE-2026-75137 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-75137 being exploited in the wild.
- How severe is CVE-2026-75137?
- Medium severity, with a CVSS score of 6.1, published 2 September 2026.
- Which products and versions are affected?
- UpSignOn for Windows before 7.19.0.
- Is there a fix for CVE-2026-75137?
- A patch was published on 2026-08-05: Fixed in version 7.19.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-75137 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-75137?
- Check whether you run UpSignOn for Windows at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a cleartext storage of sensitive information in memory (CWE-316). Even after the application locks, sensitive vault data including entry names, URLs, usernames, passwords, TOTP secrets, and notes remain unencrypted in the process memory of UpSignOn.exe. An attacker with local access and PROCESS_VM_READ permission can read this memory space and extract all sensitive fields. The attack requires local network/process access and low-level privileges but no user interaction. The vulnerability was fixed in version 7.19.0 released on 05/08/2026.
Affected products
- UpSignOn UpSignOn for Windows before 7.19.0
Timeline
- 2026-09-02: disclosed
- 2026-08-05: patched: Fixed in version 7.19.0