# CVE-2026-4387: Unencrypted storage of authentication state in StrongDM Desktop Application state.kv file

> Local attackers can read cleartext authentication tokens and keys from the state file, potentially leading to account takeover.

- **Severity:** Low 2.0 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:L/SA:L`)
- **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:** 29 May 2026
- **Updated:** 1 Jun 2026
- **Also known as:** GHSA-qgjm-4mg2-6wm5

## What is CVE-2026-4387?

CVE-2026-4387 is a low-severity vulnerability in StrongDM Desktop Application, published on 29 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

StrongDM Desktop Application before 23.74.0 (Desktop Client before 53.77.0) on Microsoft Windows stores authentication state, including a JSON Web Token and asymmetric key material, in cleartext in a per-user state file located at C:\Users\<username>\.sdm\state.kv. The file is protected only by default user-level NTFS permissions.

Exploitation requires local read access to the affected user's profile directory and additional deployment and execution conditions on the target host.

The condition was reported through coordinated disclosure by Hope Walker (SpecterOps).

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-312 (Cleartext Storage of Sensitive Information)

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


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

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

## Is CVE-2026-4387 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-4387 is a low-severity vulnerability in StrongDM Desktop Application, published on 29 May 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-4387 in the wild and no public exploit code.

Affected product: StrongDM Desktop Application. 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-4387/ (Markdown: https://insights.sbomify.com/CVE-2026-4387/index.md)
```

## Sources

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

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