CVE-2005-2827

HIGHCVSS v2 · 7.27.2—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 7.2 — v2 rates that HIGH (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:L/AC:L/Au:N/C:C/I:C/A:C. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 2.6% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Sources: epss, nvd_v2
Weaponized
7.2EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • Public exploit code is available (Exploit-DB (verified), public exploit)
CISA-KEV: Not listedEPSS PROB: 3%CVSS v2: 7.2Exploit: Exploit-DB (verified) · public exploitExposed: 0

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

The thread termination routine in the kernel for Windows NT 4.0 and 2000 (NTOSKRNL.EXE) allows local users to modify kernel memory and execution flow via steps in which a terminating thread causes Asynchronous Procedure Call (APC) entries to free the wrong data, aka the "Windows Kernel Vulnerability."

CVSS v2.0 (legacy)
7.2HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
7.2(low)
EG Risk
63(Track)
EG Risk 63/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity72% × 45%
Exploitation65% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
3%
EPSS %ILE
85%
KEV
Not listed

Published

December 14, 2005

Last Modified

April 16, 2026

References (32)

Data Freshness Timeline

(refreshed 2× in last 7d / 2× 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.

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

Publicly available exploits

(1 reference)

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

  • Exploit-DBEDB-1407✓ verified
    First seen Jan 5, 2006

    Microsoft Windows Server 2000 Kernel - APC Data-Free Local Escalation (MS05-055)

    Open source ↗

Frequently asked(4)

What is CVE-2005-2827?
CVE-2005-2827 is a high vulnerability published on December 14, 2005. The thread termination routine in the kernel for Windows NT 4.0 and 2000 (NTOSKRNL.EXE) allows local users to modify kernel memory and execution flow via steps in which a terminating thread causes Asynchronous Procedure Call (APC) entries to free the wrong data, aka the "Windows Kernel…
When was CVE-2005-2827 disclosed?
CVE-2005-2827 was first published in the National Vulnerability Database on December 14, 2005, with the most recent update on April 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2005-2827 actively exploited?
CVE-2005-2827 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3% probability of exploitation in the next 30 days, which ranks it in the top 15.4% of all scored CVEs.
How do I remediate CVE-2005-2827?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2005-2827, 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-2005-2827

Explore →

Is Your Infrastructure Affected by CVE-2005-2827?

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

Start Free Scan →Browse All CVEs