CVE-2026-4387: CWE-312 Cleartext Storage of Sensitive Information in StrongDM StrongDM Desktop Application
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).
AI Analysis
Technical Summary
StrongDM Desktop Application on Microsoft Windows prior to version 23.74.0 stores authentication state data, such as JSON Web Tokens and asymmetric key material, in cleartext within a per-user state file located at C:\Users\<username>\.sdm\state.kv. This file is protected only by default NTFS permissions, meaning any local user with read access to the profile directory could potentially access sensitive authentication information. Exploitation requires local access and additional deployment conditions. The vulnerability is categorized under CWE-312 (Cleartext Storage of Sensitive Information) and CWE-522 (Insufficiently Protected Credentials). No official patch or remediation level has been published yet by StrongDM.
Potential Impact
If an attacker gains local read access to the affected user's profile directory, they could obtain sensitive authentication tokens and key material stored in cleartext. This could potentially allow unauthorized access to StrongDM resources under the affected user's credentials. However, exploitation requires local access and additional conditions, limiting the overall risk. The CVSS score of 2.0 indicates low severity and limited impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict local access to user profile directories and ensure NTFS permissions are properly configured to limit unauthorized read access. Monitor vendor communications for updates on patches or official mitigations.
CVE-2026-4387: CWE-312 Cleartext Storage of Sensitive Information in StrongDM StrongDM Desktop Application
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).
CVSS v4.0
Score 2.0low
Affected software
pkg:github/strongdm/strongdm-desktop-applicationRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
StrongDM Desktop Application on Microsoft Windows prior to version 23.74.0 stores authentication state data, such as JSON Web Tokens and asymmetric key material, in cleartext within a per-user state file located at C:\Users\<username>\.sdm\state.kv. This file is protected only by default NTFS permissions, meaning any local user with read access to the profile directory could potentially access sensitive authentication information. Exploitation requires local access and additional deployment conditions. The vulnerability is categorized under CWE-312 (Cleartext Storage of Sensitive Information) and CWE-522 (Insufficiently Protected Credentials). No official patch or remediation level has been published yet by StrongDM.
Potential Impact
If an attacker gains local read access to the affected user's profile directory, they could obtain sensitive authentication tokens and key material stored in cleartext. This could potentially allow unauthorized access to StrongDM resources under the affected user's credentials. However, exploitation requires local access and additional conditions, limiting the overall risk. The CVSS score of 2.0 indicates low severity and limited impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict local access to user profile directories and ensure NTFS permissions are properly configured to limit unauthorized read access. Monitor vendor communications for updates on patches or official mitigations.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- StrongDM
- Date Reserved
- 2026-03-18T13:52:47.802Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a19e68ee29bf47b50037d7f
Added to database: 05/29/2026, 19:18:38 UTC
Last enriched: 06/05/2026, 21:03:24 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 92
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.