How severe is CVE-2025-6180?

CVE-2025-6180 has a CVSS 4.0 base score of 8.5, rated high severity.

Is CVE-2025-6180 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (3rd percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2025-6180?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2025-6180 have an EU (EUVD) identifier?

Yes. CVE-2025-6180 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-25352.

When was CVE-2025-6180 published?

CVE-2025-6180 was published on 2025-08-20 and last updated on 2026-06-17.

CVE-2025-6180

CVE-2025-6180 is a high-severity vulnerability with a CVSS 4.0 base score of 8.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-319.

Key facts

Severity: High (CVSS 4.0 base score 8.5)
EPSS exploit prediction: 0% (3rd percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-25352
Weakness: CWE-319
Published: 2025-08-20
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is CVE-2025-6180?: 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.
How severe is CVE-2025-6180?: CVE-2025-6180 has a CVSS 4.0 base score of 8.5, rated high severity.
Is CVE-2025-6180 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (3rd percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2025-6180?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-6180 have an EU (EUVD) identifier?: Yes. CVE-2025-6180 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-25352.
When was CVE-2025-6180 published?: CVE-2025-6180 was published on 2025-08-20 and last updated on 2026-06-17.

References

https://security.strongdm.com/?tcuUid=56fde839-9388-4361-8d3b-9baa7b2de2ed

Other CWE-319 (Cleartext Transmission of Sensitive Information) vulnerabilities

CVE-2025-4378 — Critical (CVSS 10.0): Cleartext Transmission of Sensitive Information, Use of Hard-coded Credentials vulnerability in Ataturk University…
CVE-2025-47419 — Critical (CVSS 10.0): Cleartext Transmission of Sensitive Information vulnerability in Crestron Automate VX allows Sniffing Network…
CVE-2026-48902 — Critical (CVSS 9.8): The password and username reset features created plain http links for https connections if the "Force SSL" flag wasn't…
CVE-2025-34271 — Critical (CVSS 9.8): Nagios Log Server versions prior to 2024R2.0.2 contain a vulnerability in the cluster manager component when…
CVE-2025-32880 — Critical (CVSS 9.8): An issue was discovered on COROS PACE 3 devices through 3.0808.0. It implements a function to connect the watch to a…
CVE-2025-26199 — Critical (CVSS 9.8): CloudClassroom-PHP-Project v1.0 is affected by an insecure credential transmission vulnerability. The application…

Browse all CWE-319 (Cleartext Transmission of Sensitive Information) vulnerabilities →