Vulnerability · CVE-2025-6180
The StrongDM Client insufficiently protected a pre-authentication token.
Published Aug 20, 2025 · catalog updated Aug 20, 2025 · StrongDM
Last checked Oct 29, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2025-6180. EPSS is 0.11%. Act only if a listed version of StrongDM is installed.
Gaps on this record
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
Same product and reporting
- CVE-2025-6183 · High
- CVE-2025-6181 · High
- Severity
- High8.5
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.11%
- Remediation
- Advisory link
- Affected products
- vendor StrongDM sdm-cli 0 ≤47.96.0
The StrongDM Client insufficiently protected a pre-authentication token. Attackers could exploit this to intercept and reuse the token, potentially redeeming valid authentication credentials through a race condition.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- vendor StrongDM sdm-cli 0 ≤47.96.00 ≤47.96.0
How to fix CVE-2025-6180
No stored fix
No vendor fix text is stored. Use the linked advisory before you change production.
Version check
Seen in 0 ≤47.96.0
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2025-6180. EPSS is 0.11%. Act only if a listed version of StrongDM is installed.
Which versions are affected?
Compare what you have installed with StrongDM sdm-cli 0 ≤47.96.0 0 ≤47.96.0. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 0.11%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Aug 20, 2025 · EUVD
Detected
The StrongDM Client insufficiently protected a pre-authentication token. Attackers could exploit this to intercept and reuse the token, potentially redeeming valid authentication credentials through a race condition.
Aug 20, 2025 · EUVD
Updated
The StrongDM Client insufficiently protected a pre-authentication token. Attackers could exploit this to intercept and reuse the token, potentially redeeming valid authentication credentials through a race condition.
Sources
- CVE.orgVulnerability recordCVE-2025-6180
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2025-6180
30-day exploitation probability 0.11%
first.org - EUVDVulnerability recordEUVD-2025-25352
The StrongDM Client insufficiently protected a pre-authentication token. Attackers could exploit this to intercept and reuse the token, potentially redeeming valid authentication credentials through a race condition.
euvd.enisa.europa.eu
References
Freshness
Last verified in this catalog Oct 29, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- FIRST EPSSOct 23, 2026
- CVE.orgOct 22, 2026
- EUVDOct 22, 2026