Quick answers
- Is CVE-2026-75136 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-75136 being exploited in the wild.
- How severe is CVE-2026-75136?
- 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-75136?
- A patch was published on 2026-08-05: Version 7.19.0 released with security fixes Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-75136 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-75136?
- 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 an insecure credential storage issue (CWE-522) in UpSignOn for Windows versions prior to 7.19.0. The biometric unlock key is stored in the Windows PasswordVault API without sufficient protection, allowing local attackers with standard user privileges to retrieve it from the same Windows session without triggering authentication. Once an attacker obtains the biometric key, they can decrypt the protected vault files and export the entire password manager contents in cleartext. The attack requires local network or physical access and an active Windows session but no administrative privileges. Version 7.19.0, released 05/08/2026, addresses this issue with security fixes.
Affected products
- UpSignOn UpSignOn for Windows before 7.19.0
Timeline
- 2026-09-02: disclosed
- 2026-08-05: patched: Version 7.19.0 released with security fixes