Threadlinqs IntelligenceStart free

VulnerabilityCVE-2008-4250Published 2008-10-23

CVE-2008-4250 — Microsoft Windows 2000

criticalCISA KEVRansomwarePublic exploit5 PoC repos

As of 2026-05-21, CVE-2008-4250 is a CRITICAL-severity vulnerability in Microsoft Windows 2000, CVSS v3.1 9.8, EPSS 98.7% (99.9th percentile). It is listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-05-20), with a US federal remediation deadline of 2026-06-03, and CISA links it to known ransomware campaigns. Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2008-4250, most recently “CISA KEV Catalog Adds Seven Vulnerabilities (May 20, 2026) — Microsoft Defender CVE-2026-41091 (EoP) and CVE-2026-45498 (DoS) Headline Active Exploitation Batch”.

CVSS v3.1
9.8/10Critical
EPSS
98.7%Higher than 99.9% of scored CVEs
CISA KEV
ListedAdded · due 2026-06-03
Tracked threats
1Campaigns referencing it
Priority
10/10Threadlinqs triage score
Published
Updated 2026-05-21
CVSS v3.1 9.8 (CRITICAL) · EPSS 98.7% (higher than 99.9% of all scored CVEs) · Priority 10/10 · Published 2008-10-23

Last updated:

What is CVE-2008-4250?

The Server service in Microsoft Windows 2000 SP4, XP SP2 and SP3, Server 2003 SP1 and SP2, Vista Gold and SP1, Server 2008, and 7 Pre-Beta allows remote attackers to execute arbitrary code via a crafted RPC request that triggers the overflow during path canonicalization, as exploited in the wild by Gimmiv.A in October 2008, aka "Server Service Vulnerability."

The record classifies CVE-2008-4250 under weakness classes CWE-94, CWE-119. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on confidentiality, integrity, availability. 5 affected-product entries are recorded, across 1 vendor, listed below. The identifier was first published 6579 days ago.

Severity and exploitation probability

CVSS v3.1 base score
9.8 — CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (FIRST)
98.7% probability of exploitation in the next 30 days, higher than 99.9% of all scored CVEs
CISA KEV
Listed since 2026-05-20, federal remediation deadline 2026-06-03 — used in known ransomware campaigns
Threadlinqs priority
10/10 — CISA lists it as used in ransomware, which Threadlinqs scores at the maximum
Published
2008-10-23, last modified 2026-05-21

Is CVE-2008-4250 being exploited?

CISA added CVE-2008-4250 to the Known Exploited Vulnerabilities catalog on 2026-05-20, which means the agency holds evidence of exploitation in the wild; US federal civilian agencies had to remediate it by 2026-06-03 under BOD 22-01. CISA flags the vulnerability as one used in known ransomware campaigns. Weaponised exploit code for CVE-2008-4250 is publicly available. 5 public proof-of-concept repositories are tracked for this identifier. It currently carries a trending score of 48 in the Threadlinqs vulnerability feed.

Affected products and versions

  • Microsoft: Windows 2000, Windows Server 2003, Windows Server 2008, Windows Vista, Windows Xp

How to fix CVE-2008-4250

The record marks a vendor fix as available for CVE-2008-4250. Patch reference: https://docs.microsoft.com/en-us/security-updates/securitybulletins/2008/ms08-067. Vendor advisory: http://secunia.com/advisories/32326. Because CVE-2008-4250 is KEV-listed, US federal civilian agencies were required to apply the vendor fix, or stop using the product, by 2026-06-03. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

Threat activity tracking CVE-2008-4250

1 tracked threat in the Threadlinqs corpus references CVE-2008-4250, either in the campaign’s CVE list or as an indicator on the campaign record.

Sources

Enriched from CVE.org, FIRST EPSS, CISA KEV, GitHub Security Advisories, public proof-of-concept repositories. Last verified by Threadlinqs on .

Vendor advisory and patch

Exploit and proof of concept

Third-party advisory

Vulnerability database entry

Mailing list and disclosure

Other references