What is CVE-2026-4387?
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\\.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).
The record classifies CVE-2026-4387 under weakness classes CWE-312, CWE-522. 2 affected-product entries are recorded, across 1 vendor, listed below. The identifier was first published 134 days ago.
Severity and exploitation probability
- CVSS v4.0 base score
- 2 — Low (derived from score)
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 - EPSS (FIRST)
- 0.1% probability of exploitation in the next 30 days, higher than 2.5% of all scored CVEs
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 1.1/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2026-05-29, last modified 2026-06-01
Is CVE-2026-4387 being exploited?
It currently carries a trending score of 6 in the Threadlinqs vulnerability feed.
Affected products and versions
- StrongDM: Desktop Application, Desktop Client
How to fix CVE-2026-4387
No vendor patch reference has been recorded for CVE-2026-4387 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.
Threat activity tracking CVE-2026-4387
1 tracked threat in the Threadlinqs corpus references CVE-2026-4387, either in the campaign’s CVE list or as an indicator on the campaign record.
Sources
Enriched from CVE.org, FIRST EPSS, GitHub Security Advisories. Last verified by Threadlinqs on .