# CVE-2026-75137: UpSignOn < 7.19.0 Sensitive Data Exposure in Process Memory after Lock

> Local attackers can read cleartext vault data from process memory after locking, exposing sensitive credentials and secrets.

- **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-qgm4-q464-4557

## What is CVE-2026-75137?

CVE-2026-75137 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 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.

Weakness: CWE-316 (Cleartext Storage of Sensitive Information in Memory)

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


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

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

## Is CVE-2026-75137 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-75137 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-75137 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-75137/ (Markdown: https://insights.sbomify.com/CVE-2026-75137/index.md)
```

## Sources

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

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