CVE-2025-7771

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.7 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 40% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
8.7
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 7%CVSS: 8.7Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

ThrottleStop.sys, a legitimate driver, exposes two IOCTL interfaces that allow arbitrary read and write access to physical memory via the MmMapIoSpace function. This insecure implementation can be exploited by a malicious user-mode application to patch the running Windows kernel and invoke arbitrary kernel functions with ring-0 privileges. The vulnerability enables local attackers to execute arbitrary code in kernel context, resulting in privilege escalation and potential follow-on attacks, such as disabling security software or bypassing kernel-level protections. ThrottleStop.sys version 3.0.0.0 and possibly others are affected. Apply updates per vendor instructions.

CVSS v3
8.7
EG Score
8.7(medium)
EPSS
93.3%
KEV
Not listed

Published

August 6, 2025

Last Modified

June 17, 2026

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 39× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 107 total refreshes for this CVE.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:24 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:30 UTCEPSS rescore
  5. 2026-07-19 14:30 UTCEPSS rescore
  6. 2026-07-19 02:28 UTCEPSS rescore
  7. 2026-07-19 02:28 UTCEPSS rescore
  8. 2026-07-18 10:04 UTCEPSS rescore
  9. 2026-07-18 10:04 UTCEPSS rescore
  10. 2026-07-16 17:02 UTCEPSS rescore
  11. 2026-07-16 17:02 UTCEPSS rescore
  12. 2026-07-15 16:57 UTCEPSS rescore
  13. 2026-07-15 16:57 UTCEPSS rescore
  14. 2026-07-13 06:12 UTCEPSS rescore
  15. 2026-07-12 05:46 UTCEPSS rescore
  16. 2026-07-12 05:46 UTCEPSS rescore
  17. 2026-07-11 08:27 UTCEPSS rescore
  18. 2026-07-11 08:27 UTCEPSS rescore
  19. 2026-07-09 19:10 UTCEPSS rescore
  20. 2026-07-08 15:15 UTCEPSS rescore
  21. 2026-07-07 13:46 UTCEPSS rescore
  22. 2026-07-06 16:27 UTCEPSS rescore
  23. 2026-07-05 02:30 UTCEPSS rescore
  24. 2026-07-05 02:30 UTCEPSS rescore
  25. 2026-07-04 06:31 UTCEPSS rescore
Show 75 more
  1. 2026-07-04 06:31 UTCEPSS rescore
  2. 2026-07-01 15:06 UTCEPSS rescore
  3. 2026-06-30 23:22 UTCEPSS rescore
  4. 2026-06-30 23:22 UTCEPSS rescore
  5. 2026-06-29 14:06 UTCEPSS rescore
  6. 2026-06-29 14:06 UTCEPSS rescore
  7. 2026-06-28 04:56 UTCEPSS rescore
  8. 2026-06-28 04:56 UTCEPSS rescore
  9. 2026-06-27 03:08 UTCEPSS rescore
  10. 2026-06-25 13:49 UTCEPSS rescore
  11. 2026-06-25 13:49 UTCEPSS rescore
  12. 2026-06-24 14:05 UTCEPSS rescore
  13. 2026-06-24 14:04 UTCEPSS rescore
  14. 2026-06-23 21:32 UTCEPSS rescore
  15. 2026-06-22 14:25 UTCEPSS rescore
  16. 2026-06-22 14:25 UTCEPSS rescore
  17. 2026-06-21 01:59 UTCEPSS rescore
  18. 2026-06-21 01:59 UTCEPSS rescore
  19. 2026-06-19 19:25 UTCEPSS rescore
  20. 2026-06-19 19:25 UTCEPSS rescore
  21. 2026-06-18 17:52 UTCEPSS rescore
  22. 2026-06-18 17:52 UTCEPSS rescore
  23. 2026-06-17 17:53 UTCEPSS rescore
  24. 2026-06-16 17:52 UTCEPSS rescore
  25. 2026-06-15 17:48 UTCEPSS rescore
  26. 2026-06-14 23:18 UTCEPSS rescore
  27. 2026-06-13 23:00 UTCEPSS rescore
  28. 2026-06-13 23:00 UTCEPSS rescore
  29. 2026-06-12 23:12 UTCEPSS rescore
  30. 2026-06-12 23:12 UTCEPSS rescore
  31. 2026-06-11 14:00 UTCEPSS rescore
  32. 2026-06-10 22:18 UTCEPSS rescore
  33. 2026-06-10 13:22 UTCEPSS rescore
  34. 2026-06-08 15:49 UTCEG score recompute 8.70
  35. 2026-06-08 15:49 UTCGHSA enrichment
  36. 2026-06-08 14:17 UTCEPSS rescore
  37. 2026-06-08 14:17 UTCEPSS rescore
  38. 2026-06-07 15:24 UTCEPSS rescore
  39. 2026-06-07 15:24 UTCEPSS rescore
  40. 2026-06-06 13:47 UTCEPSS rescore
  41. 2026-06-06 13:47 UTCEPSS rescore
  42. 2026-06-05 22:47 UTCEPSS rescore
  43. 2026-06-05 22:46 UTCEPSS rescore
  44. 2026-06-05 06:10 UTCEPSS rescore
  45. 2026-06-05 06:10 UTCEPSS rescore
  46. 2026-06-04 13:12 UTCEPSS rescore
  47. 2026-06-04 13:12 UTCEPSS rescore
  48. 2026-06-02 20:13 UTCEPSS rescore
  49. 2026-06-01 13:51 UTCEPSS rescore
  50. 2026-06-01 13:51 UTCEPSS rescore
  51. 2026-05-31 22:30 UTCEPSS rescore
  52. 2026-05-31 22:30 UTCEPSS rescore
  53. 2026-05-31 00:16 UTCEPSS rescore
  54. 2026-05-31 00:16 UTCEPSS rescore
  55. 2026-05-29 13:44 UTCEPSS rescore
  56. 2026-05-29 13:44 UTCEPSS rescore
  57. 2026-05-28 13:44 UTCEPSS rescore
  58. 2026-05-28 13:44 UTCEPSS rescore
  59. 2026-05-28 13:44 UTCEPSS rescore
  60. 2026-05-27 13:40 UTCEPSS rescore
  61. 2026-05-27 13:40 UTCEPSS rescore
  62. 2026-05-27 13:40 UTCEPSS rescore
  63. 2026-05-27 13:40 UTCEPSS rescore
  64. 2026-05-26 13:44 UTCEPSS rescore
  65. 2026-05-26 13:44 UTCEPSS rescore
  66. 2026-05-26 13:44 UTCEPSS rescore
  67. 2026-05-26 07:18 UTCEPSS rescore
  68. 2026-05-26 07:18 UTCEPSS rescore
  69. 2026-05-26 07:18 UTCEPSS rescore
  70. 2026-05-24 16:58 UTCEPSS rescore
  71. 2026-05-22 21:16 UTCEPSS rescore
  72. 2026-05-22 21:16 UTCEPSS rescore
  73. 2026-05-21 22:43 UTCEPSS rescore
  74. 2026-05-21 10:16 UTCEG score recompute
  75. 2026-05-21 10:16 UTCGHSA enrichment

Publicly available exploits

(10 references)

Working exploit code is in the public domain (9 GitHub PoCs) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-52512
    First seen Apr 22, 2026

    Throttlestop Kernel Driver - Kernel Out-of-Bounds Write Privilege Escalation

    Open source ↗
  • GitHub PoCD4rkks/CVE-2025-7771-Vulnerability-Exploration
    First seen Apr 17, 2026

    Escalating privilege in the system from unsigned driver using throttlestop vulnerability

    Open source ↗
  • GitHub PoCDeathShotXD/0xKern3lCrush
    First seen Feb 4, 2026

    Advanced PoC & Research for CVE-2026-0828 (Safetica) and CVE-2025-7771 (ThrottleStop). Analysis of BYOVD (Bring Your Own Vulnerable Driver) TTPs for Ring 0 process termination and physical memory R/W. Researching EDR-Killer patterns, PPL bypasses, and kernel-mode primitives used by MedusaLocker and other threat actors.

    Open source ↗
  • GitHub PoClzty/CVE-2025-7771
    First seen Jan 21, 2026

    This Poc demonstrate Arbitrary read/write primitives provided by CVE-2025-7771

    Open source ↗
  • GitHub PoCxM0kht4r/CVE-2025-7771
    First seen Jan 13, 2026

    A simple PoC demonstrating the vulnerability in the ThrottleStop.sys driver, showcasing arbitrary physical memory read and write capabilities, as well as virtual-to-physical address translation using Superfetch.

    Open source ↗
  • GitHub PoCv31l0x1/ThrottleStopPPL
    First seen Dec 31, 2025

    Poc for CVE-2025-7771 to modify PPL Protection

    Open source ↗
  • GitHub PoCAmrHuss/throttlestop-exploit-rw
    First seen Nov 13, 2025

    Arbitrary physical memory read/write exploitation using ThrottleStop.sys (CVE-2025-7771) with superfetch address translation - Windows kernel security research

    Open source ↗
  • GitHub PoCGabriel-Lacorte/CVE-2025-7771
    First seen Oct 3, 2025

    Arbitrary Function Call Exploit using the ThrottleStop driver

    Open source ↗
  • GitHub PoCDemoo1337/ThrottleStop
    First seen Sep 7, 2025

    CVE-2025-7771 ThrottleStop.sys privilege escalation exploit - unrestricted IOCTL access to physical memory via MmMapIoSpace

    Open source ↗
  • GitHub PoCfxrstor/ThrottleStopPoC
    First seen Aug 31, 2025

    CVE-2025-7771: Arbitrary physical memory and I/O port read/write via ThrottleStop driver

    Open source ↗

Frequently asked(5)

What is CVE-2025-7771?
CVE-2025-7771 is a high vulnerability published on August 6, 2025. ThrottleStop.sys, a legitimate driver, exposes two IOCTL interfaces that allow arbitrary read and write access to physical memory via the MmMapIoSpace function. This insecure implementation can be exploited by a malicious user-mode application to patch the running Windows kernel and invoke…
When was CVE-2025-7771 disclosed?
CVE-2025-7771 was first published in the National Vulnerability Database on August 6, 2025, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-7771 actively exploited?
CVE-2025-7771 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 93.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-7771?
CVE-2025-7771 has a CVSS v3 base score of 8.7 (NVD).
How do I remediate CVE-2025-7771?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-7771, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-7771

Explore →

Is Your Infrastructure Affected by CVE-2025-7771?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.