How severe is CVE-2025-64701?

CVE-2025-64701 has a CVSS 3.x base score of 7.8, 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 high.

Is CVE-2025-64701 being actively exploited?

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

How do I fix CVE-2025-64701?

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

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

When was CVE-2025-64701 published?

CVE-2025-64701 was published on 2025-12-11 and last updated on 2026-06-17.

CVE-2025-64701

CVE-2025-64701 is a high-severity vulnerability with a CVSS 3.x base score of 7.8. 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-268.

Key facts

Severity: High (CVSS 3.x base score 7.8)
CVSS v4: 8.5
EPSS exploit prediction: 0% (2nd percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-202666
Weakness: CWE-268
Published: 2025-12-11
Last modified: 2026-06-17

Description

QND Premium/Advance/Standard Ver.11.0.9i and prior contains a privilege escalation vulnerability, which may allow a user who can log in to a Windows system with the affected product to gain administrator privileges. As a result, sensitive information may be accessed or altered, and arbitrary actions may be performed.

Frequently asked questions

What is CVE-2025-64701?: QND Premium/Advance/Standard Ver.11.0.9i and prior contains a privilege escalation vulnerability, which may allow a user who can log in to a Windows system with the affected product to gain administrator privileges. As a result, sensitive information may be accessed or altered, and arbitrary actions may be performed.
How severe is CVE-2025-64701?: CVE-2025-64701 has a CVSS 3.x base score of 7.8, 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 high.
Is CVE-2025-64701 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (2nd percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2025-64701?: 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-64701 have an EU (EUVD) identifier?: Yes. CVE-2025-64701 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-202666.
When was CVE-2025-64701 published?: CVE-2025-64701 was published on 2025-12-11 and last updated on 2026-06-17.

References

Other CWE-268 vulnerabilities

CVE-2024-4877 — High (CVSS 8.8): OpenVPN version 2.4.0 through 2.6.10 on Windows allows an external, lesser privileged process to create a named pipe…
CVE-2023-0759 — High (CVSS 8.8): Privilege Chaining in GitHub repository cockpit-hq/cockpit prior to 2.3.8.
CVE-2025-7973 — High (CVSS 8.5): A security issue exists in FactoryTalk ViewPoint version 14.0 or below due to improper handling of MSI repair…
CVE-2026-32325 — High (CVSS 7.8): Privilege chaining issue exists in ServerView Agents for Windows V11.60.04 and earlier. If this vulnerability is…
CVE-2026-3888 — High (CVSS 7.8): Local privilege escalation in snapd on Linux allows local attackers to get root privilege by re-creating snap's private…
CVE-2025-2297 — High (CVSS 7.8): Prior to version 25.4.270.0, a local authenticated attacker can manipulate user profile files to add illegitimate…

Browse all CWE-268 vulnerabilities →