How severe is CVE-2025-9317?

CVE-2025-9317 has a CVSS 3.x base score of 8.4, rated high severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.

Is CVE-2025-9317 being actively exploited?

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

How do I fix CVE-2025-9317?

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-9317 have an EU (EUVD) identifier?

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

When was CVE-2025-9317 published?

CVE-2025-9317 was published on 2025-11-15 and last updated on 2026-06-17.

CVE-2025-9317

CVE-2025-9317 is a high-severity vulnerability with a CVSS 3.x base score of 8.4. 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-327.

Key facts

Severity: High (CVSS 3.x base score 8.4)
CVSS v4: 8.3
EPSS exploit prediction: 0% (1st percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-197663
Weakness: CWE-327
Published: 2025-11-15
Last modified: 2026-06-17

Description

The vulnerability, if exploited, could allow a miscreant with read access to Edge Project files or Edge Offline Cache files to reverse engineer Edge users' app-native or Active Directory passwords through computational brute-forcing of weak hashes.

Frequently asked questions

What is CVE-2025-9317?: The vulnerability, if exploited, could allow a miscreant with read access to Edge Project files or Edge Offline Cache files to reverse engineer Edge users' app-native or Active Directory passwords through computational brute-forcing of weak hashes.
How severe is CVE-2025-9317?: CVE-2025-9317 has a CVSS 3.x base score of 8.4, rated high severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2025-9317 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (1st percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2025-9317?: 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-9317 have an EU (EUVD) identifier?: Yes. CVE-2025-9317 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-197663.
When was CVE-2025-9317 published?: CVE-2025-9317 was published on 2025-11-15 and last updated on 2026-06-17.

References

Other CWE-327 (Use of a Broken or Risky Cryptographic Algorithm) vulnerabilities

CVE-2026-50086 — Critical (CVSS 10.0): The Aqara IAM/SSO gateway (gw-builder.aqara.com) exposes bidirectional AES round-trups against the platform's signing…
CVE-2026-21718 — Critical (CVSS 10.0): An authentication bypass vulnerability exists in Copeland XWEB Pro version 1.12.1 and prior, enabling any attackers to…
CVE-2025-54426 — Critical (CVSS 9.9): Polkadot Frontier is an Ethereum and EVM compatibility layer for Polkadot and Substrate. In versions prior to commit…
CVE-2024-51478 — Critical (CVSS 9.9): YesWiki is a wiki system written in PHP. Prior to 4.4.5, the use of a weak cryptographic algorithm and a hard-coded…
CVE-2026-28252 — Critical (CVSS 9.8): A Use of a Broken or Risky Cryptographic Algorithm vulnerability in Trane Tracer SC, Tracer SC+, and Tracer Concierge…
CVE-2025-13476 — Critical (CVSS 9.8): Rakuten Viber Cloak mode in Android v25.7.2.0g and Windows v25.6.0.0–v25.8.1.0 uses a static and predictable TLS…

Browse all CWE-327 (Use of a Broken or Risky Cryptographic Algorithm) vulnerabilities →