CVE-2024-38063
Windows TCP/IP Remote Code Execution Vulnerability
- CVSS
- 9.8Criticalscored by the publisher (CNA)
- Exploited in the wild
- Not knownUnvetted proof-of-concept code on GitHub; not in CISA KEV
- EPSS
- 73.6%chance of exploitation in the next 30 daystop 0.6% of scored CVEsFIRST score of 11 Nov 2026
- Fix
- Patch availablesee the advisories in the references
- Published
- 13 Aug 2024analysed here 12 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.20751Vendor says fixed in: not stated | |
| Microsoft Windows 10 Version 1607 | >= 10.0.14393.0 and < 10.0.14393.7259Vendor says fixed in: not stated | |
| Microsoft Windows 10 Version 1809 | >= 10.0.17763.0 and < 10.0.17763.6293Vendor says fixed in: not stated | |
| Microsoft Windows 10 Version 21H2 | >= 10.0.19043.0 and < 10.0.19044.4780Vendor says fixed in: not stated | |
| Microsoft Windows 10 Version 22H2 | >= 10.0.19045.0 and < 10.0.19045.4780Vendor says fixed in: not stated | |
| Microsoft Windows 11 version 21H2 | >= 10.0.0 and < 10.0.22000.3197Vendor says fixed in: not stated | |
| Microsoft Windows 11 version 22H2 | >= 10.0.22621.0 and < 10.0.22621.4037Vendor says fixed in: not stated | |
| Microsoft Windows 11 version 22H3 | >= 10.0.22631.0 and < 10.0.22631.4037Vendor says fixed in: not stated | |
| Microsoft Windows 11 Version 23H2 | >= 10.0.22631.0 and < 10.0.22631.4037Vendor says fixed in: not stated | |
| Microsoft Windows 11 Version 24H2 | >= 10.0.26100.0 and < 10.0.26100.1457Vendor says fixed in: not stated | |
| Microsoft Windows Server 2008 R2 Service Pack 1 | >= 6.1.7601.0 and < 6.1.7601.27277Vendor says fixed in: not stated | |
| Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation) | >= 6.1.7601.0 and < 6.1.7601.27277Vendor says fixed in: not stated | |
| Microsoft Windows Server 2008 Service Pack 2 | >= 6.0.6003.0 and < 6.0.6003.22825Vendor says fixed in: not stated | |
| Microsoft Windows Server 2008 Service Pack 2 | >= 6.0.6003.0 and < 6.0.6003.22825Vendor says fixed in: not stated | |
| Microsoft Windows Server 2008 Service Pack 2 (Server Core installation) | >= 6.0.6003.0 and < 6.0.6003.22825Vendor says fixed in: not stated | |
| Microsoft Windows Server 2012 | >= 6.2.9200.0 and < 6.2.9200.25031Vendor says fixed in: not stated | |
| Microsoft Windows Server 2012 R2 | >= 6.3.9600.0 and < 6.3.9600.22134Vendor says fixed in: not stated | |
| Microsoft Windows Server 2012 R2 (Server Core installation) | >= 6.3.9600.0 and < 6.3.9600.22134Vendor says fixed in: not stated | |
| Microsoft Windows Server 2012 (Server Core installation) | >= 6.2.9200.0 and < 6.2.9200.25031Vendor says fixed in: not stated | |
| Microsoft Windows Server 2016 | >= 10.0.14393.0 and < 10.0.14393.7259Vendor says fixed in: not stated | |
| Microsoft Windows Server 2016 (Server Core installation) | >= 10.0.14393.0 and < 10.0.14393.7259Vendor says fixed in: not stated | |
| Microsoft Windows Server 2019 | >= 10.0.17763.0 and < 10.0.17763.6293Vendor says fixed in: not stated | |
| Microsoft Windows Server 2019 (Server Core installation) | >= 10.0.17763.0 and < 10.0.17763.6293Vendor says fixed in: not stated | |
| Microsoft Windows Server 2022 | >= 10.0.20348.0 and < 10.0.20348.2700Vendor says fixed in: not stated | |
| Microsoft Windows Server 2022, 23H2 Edition (Server Core installation) | >= 10.0.25398.0 and < 10.0.25398.1085Vendor 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_11_24h2
- 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? Partly. The bug can be reached over the network, so generic WAF rules may stop some attacks. Its weakness type is unknown, so we cannot be more precise.
Also consider: patch
Based on the weakness type only; no CVE-specific evidence yet. 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: 32 GitHub proofs of concept
- CISA SSVC
- exploitation poc, automatable yes, technical impact totalAssessed by CISA 29 Aug 2024 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
GitHub proofs of concept
- ynwarcs/CVE-2024-38063689 stars
- Sachinart/CVE-2024-38063-poc86 stars
- ThemeHackers/CVE-2024-3806345 stars
- patchpoint/CVE-2024-3806320 stars
and 28 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
- 13 Aug 2024Published
- 15 Aug 2024First proof-of-concept repository on GitHub (unvetted)1 day later
- 29 Aug 2024CISA SSVC assessment: exploitation poc15 days later
- 10 Jul 2025CVE record last updated315 days (about 11 months) later
- 12 Nov 2026Analysed by vulneraibility.com490 days (about 1 year) later
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
| Metric | Value | What it means |
|---|---|---|
| Attack vector | NetworkReachable over the internet or any routable network. | Reachable over the internet or any routable network. |
| Attack complexity | LowRepeatable attack, no special conditions. | Repeatable attack, no special conditions. |
| Privileges required | NoneThe attacker needs no prior access. | The attacker needs no prior access. |
| 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-38063 being exploited?
Not confirmed. CVE-2024-38063 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 74% probability of exploitation in the next 30 days.
How severe is CVE-2024-38063?
CVE-2024-38063 is rated Critical with a CVSS score of 9.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-38063?
Yes. A fix has been recorded for CVE-2024-38063. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2024-38063 affect?
CVE-2024-38063 affects microsoft:windows_10_1507, microsoft:windows_10_1607, microsoft:windows_10_1809, microsoft:windows_10_21h2, and 11 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-38063
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.