# CVE-2026-75136: UpSignOn < 7.19.0 Biometric Key Exposure via Windows PasswordVault

> Local attackers can retrieve biometric keys from Windows PasswordVault to decrypt and export password manager contents in cleartext.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Sep 2026
- **Updated:** 3 Sep 2026
- **Also known as:** GHSA-9pfj-rxxp-9cf2

## What is CVE-2026-75136?

CVE-2026-75136 is a medium-severity vulnerability in Septeo IT Solutions UpSignOn, published on 2 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

UpSignOn for Windows before 7.19.0 contains an insecure credential storage vulnerability that allows local attackers to retrieve the biometric unlock key stored in the Windows PasswordVault API without triggering any authentication prompt. Attackers can access the stored biometric key from a standard local process within the same Windows session to decrypt the protected vault files and export the entire password manager contents in cleartext.

Weakness: CWE-522 (Insufficiently Protected Credentials)

## Which versions are affected by CVE-2026-75136?


## How do I fix CVE-2026-75136?

No fix has been published for CVE-2026-75136 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-75136 being exploited?

There is no known exploitation of CVE-2026-75136 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-75136 and fix it if it is affected.

What it is: CVE-2026-75136 is a medium-severity vulnerability in Septeo IT Solutions UpSignOn, published on 2 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-75136 in the wild and no public exploit code.

Affected product: Septeo IT Solutions UpSignOn. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-75136/ (Markdown: https://insights.sbomify.com/CVE-2026-75136/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-75136
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-75136
- OSV: https://osv.dev/vulnerability/CVE-2026-75136

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-75136/
Summaries are generated and may contain mistakes; the official description above is the record.