High 7.8Patch available
CVE-2024-26229
Windows CSC Service Elevation of Privilege Vulnerability
How scary is it?
updated 22 Nov 2026- No
Works without logging in1
Needs a login: a basic user account (CVSS PR:L).
- No
Reachable over the network1
Needs local access to the machine, such as a shell or a logged-in user (CVSS AV:L).
- Yes
Proof-of-concept code is public2
10 GitHub proofs of concept. GitHub proofs of concept are unvetted: some are fake or carry malware. No Exploit-DB entry or Metasploit exploit module on record.
- None known
Attacks seen in the wild1
None reported that we know of. CISA's SSVC assessment says exploitation: poc.
- No
On CISA's exploited list3
Not in the catalog as of our last sync.
Scare-o-meter
Routine patch
Serious on paper, with no sign of attacks that we know of. Patch in your normal cycle.
- Low signal
- Routine patch
- Act this week
- Drop everything
Why: our alert rule found no exploitation evidence and no easy remote attack path in the data we hold. Read from the same rule that decides our alert emails.
Are you affected? only if all are true
You run one of these 24 products in an affected versionMicrosoft Windows 10 Version 1507 / Microsoft Windows 10 Version 1607 / Microsoft Windows 10 Version 1809 (+21 more)
Microsoft Windows 10 Version 1507: >= 10.0.10240.0 and < 10.0.10240.20596
Microsoft Windows 10 Version 1607: >= 10.0.14393.0 and < 10.0.14393.6897
Microsoft Windows 10 Version 1809: >= 10.0.17763.0 and < 10.0.17763.5696, >= 10.0.0 and < 10.0.17763.5696
Microsoft Windows 10 Version 21H2: >= 10.0.19043.0 and < 10.0.19044.4291
Microsoft Windows 10 Version 22H2: >= 10.0.19045.0 and < 10.0.19045.4291
Microsoft Windows 11 version 21H2: >= 10.0.0 and < 10.0.22000.2899
Microsoft Windows 11 version 22H2: >= 10.0.22621.0 and < 10.0.22621.3447
Microsoft Windows 11 version 22H3: >= 10.0.22631.0 and < 10.0.22631.3447
And 16 more in the table below.
As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.
See the affected products table · Source 1
The attacker already has local access to the machine
CVSS attack vector: Local (AV:L). Local access required, such as a shell or a logged-in user.
Source 1
The attacker has a user account
CVSS privileges required: Low (PR:L). The attacker needs basic user privileges.
Source 1
Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.
What to do
Per our analysisA patch is available
The CVE record we hold states no fixed release number. See the advisories in the references.
- CVSS
- 7.8Highscored by the publisher (CNA)
- Exploited in the wild
- Not knownUnvetted proof-of-concept code on GitHub; not in CISA KEV
- EPSS
- 9.4%chance of exploitation in the next 30 daystop 5% of scored CVEsFIRST score of 21 Nov 2026
- Fix
- Patch availablesee the advisories in the references
- Published
- 9 Apr 2024analysed here 22 Nov 2026
Summary
Triage
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| Microsoft Windows 10 Version 1507 | >= 10.0.10240.0 and < 10.0.10240.20596Vendor says fixed in: not stated | |
| Microsoft Windows 10 Version 1607 | >= 10.0.14393.0 and < 10.0.14393.6897Vendor says fixed in: not stated | |
| Microsoft Windows 10 Version 1809 | >= 10.0.17763.0 and < 10.0.17763.5696>= 10.0.0 and < 10.0.17763.5696Vendor says fixed in: not stated | |
| Microsoft Windows 10 Version 21H2 | >= 10.0.19043.0 and < 10.0.19044.4291Vendor says fixed in: not stated | |
| Microsoft Windows 10 Version 22H2 | >= 10.0.19045.0 and < 10.0.19045.4291Vendor says fixed in: not stated | |
| Microsoft Windows 11 version 21H2 | >= 10.0.0 and < 10.0.22000.2899Vendor says fixed in: not stated | |
| Microsoft Windows 11 version 22H2 | >= 10.0.22621.0 and < 10.0.22621.3447Vendor says fixed in: not stated | |
| Microsoft Windows 11 version 22H3 | >= 10.0.22631.0 and < 10.0.22631.3447Vendor says fixed in: not stated | |
| Microsoft Windows 11 Version 23H2 | >= 10.0.22631.0 and < 10.0.22631.3447Vendor says fixed in: not stated | |
| Microsoft Windows Server 2008 R2 Service Pack 1 | >= 6.1.7601.0 and < 6.1.7601.27067Vendor says fixed in: not stated | |
| Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation) | >= 6.1.7601.0 and < 6.1.7601.27067Vendor says fixed in: not stated | |
| Microsoft Windows Server 2008 Service Pack 2 | >= 6.0.6003.0 and < 6.0.6003.22618Vendor says fixed in: not stated | |
| Microsoft Windows Server 2008 Service Pack 2 | >= 6.0.6003.0 and < 6.0.6003.22618Vendor says fixed in: not stated | |
| Microsoft Windows Server 2008 Service Pack 2 (Server Core installation) | >= 6.0.6003.0 and < 6.0.6003.22618Vendor says fixed in: not stated | |
| Microsoft Windows Server 2012 | >= 6.2.9200.0 and < 6.2.9200.24821Vendor says fixed in: not stated | |
| Microsoft Windows Server 2012 R2 | >= 6.3.9600.0 and < 6.3.9600.21924Vendor says fixed in: not stated | |
| Microsoft Windows Server 2012 R2 (Server Core installation) | >= 6.3.9600.0 and < 6.3.9600.21924Vendor says fixed in: not stated | |
| Microsoft Windows Server 2012 (Server Core installation) | >= 6.2.9200.0 and < 6.2.9200.24821Vendor says fixed in: not stated | |
| Microsoft Windows Server 2016 | >= 10.0.14393.0 and < 10.0.14393.6897Vendor says fixed in: not stated | |
| Microsoft Windows Server 2016 (Server Core installation) | >= 10.0.14393.0 and < 10.0.14393.6897Vendor says fixed in: not stated | |
| Microsoft Windows Server 2019 | >= 10.0.17763.0 and < 10.0.17763.5696Vendor says fixed in: not stated | |
| Microsoft Windows Server 2019 (Server Core installation) | >= 10.0.17763.0 and < 10.0.17763.5696Vendor says fixed in: not stated | |
| Microsoft Windows Server 2022 | >= 10.0.20348.0 and < 10.0.20348.2402Vendor says fixed in: not stated | |
| Microsoft Windows Server 2022, 23H2 Edition (Server Core installation) | >= 10.0.25398.0 and < 10.0.25398.830Vendor says fixed in: not stated |
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
Products named in our analysis
- microsoft:windows_10_1507
- microsoft:windows_10_1607
- microsoft:windows_10_1809
- microsoft:windows_10_21h2
- microsoft:windows_10_22h2
- microsoft:windows_11_21h2
- microsoft:windows_11_22h2
- microsoft:windows_11_23h2
- microsoft:windows_server_2008
- microsoft:windows_server_2012
- microsoft:windows_server_2016
- microsoft:windows_server_2019
- microsoft:windows_server_2022
- microsoft:windows_server_2022_23h2
Fix and mitigation
WAF and other mitigations
Can a WAF block it? No. The attack needs local access to the machine, so a WAF is not on its path.
Also consider: patch
Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Not listed as of our last sync.
- Public exploit code
- Unvetted proof-of-concept code on GitHub: 10 GitHub proofs of concept
- CISA SSVC
- exploitation poc, automatable no, technical impact totalAssessed by CISA 13 Jun 2024 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
GitHub proofs of concept
- RalfHacker/CVE-2024-26229-exploit145 stars
- Cracked5pider/eop24-2622941 stars
- apkc/CVE-2024-26229-BOF29 stars
- team-MineDEV/CVE-2024-2622911 stars
and 6 more repositories
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
Timeline
- 9 Apr 2024Published
- 10 Jun 2024First proof-of-concept repository on GitHub (unvetted)61 days (about 2 months) later
- 13 Jun 2024CISA SSVC assessment: exploitation poc3 days later
- 3 May 2025CVE record last updated324 days (about 11 months) later
- 22 Nov 2026Analysed by vulneraibility.com568 days (about 2 years) later
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
| Metric | Value | What it means |
|---|---|---|
| Attack vector | LocalLocal access required (shell, logged-in user). | Local access required (shell, logged-in user). |
| Attack complexity | LowRepeatable attack, no special conditions. | Repeatable attack, no special conditions. |
| Privileges required | LowThe attacker needs basic user privileges. | The attacker needs basic user privileges. |
| User interaction | NoneNo victim action needed. | No victim action needed. |
| Scope | UnchangedImpact stays within the vulnerable component. | Impact stays within the vulnerable component. |
| Confidentiality | HighTotal data disclosure possible. | Total data disclosure possible. |
| Integrity | HighComplete modification possible. | Complete modification possible. |
| Availability | HighFull outage possible. | Full outage possible. |
Common questions
Is CVE-2024-26229 being exploited?
Not confirmed. CVE-2024-26229 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 9.4% probability of exploitation in the next 30 days.
How severe is CVE-2024-26229?
CVE-2024-26229 is rated High with a CVSS score of 7.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2024-26229?
Yes. A fix has been recorded for CVE-2024-26229. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2024-26229 affect?
CVE-2024-26229 affects microsoft:windows_10_1507, microsoft:windows_10_1607, microsoft:windows_10_1809, microsoft:windows_10_21h2, and 10 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
1 reference in the CVE record, grouped by the tags the record gives them.
Advisories (1)
- msrc.microsoft.com /update-guide/vulnerability/CVE-2024-26229
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.