CVE-2026-83844
๐ MediumMicrosoft Paint on Windows. The version string is an 11.x app version rather than a Windows build number, which points to the Paint app being serviced through the Microsoft Store rather than a cumulative update โ the record does not say so and this was not confirmed, but it decides whether the fix arrives through Windows Update at all ยท 11.0.0.0 up to but excluding 11.2609.401.0 (record revised 10/11/2026; it previously gave 11.2605.91.0 as the bound). The record states no fixed version explicitly; 11.2609.401.0 is simply the lower bound of the unaffected range
CVSS (Koffei note)
7.0CVSS (v3.1, CVE List)
7.0EPSS (2026-11-18)
0.384%33.13th percentile
Exploitation
No โ no exploitation reported. SSVC 13/10/2026: exploitation none, automatable no, technical impact total ; not in CISA KEV, and the record carries no
exploit-tagged reference. Microsoft's own temporal metric agrees at E:U, unproven. Neither CISA KEV nor its JSON feed could be reached in this run, so the KEV status comes from the record's CISA-ADP container. cyberveille has no alert for this id, over a feed covering 28/09 to 04/11/2026 Existing PoC (not opened), recorded from the proof-of-concept list supplied on 09/11/2026. The CVE record carries no exploit-tagged reference and its SSVC does not record a proof of concept, so the supplied list is the only source for this and it is recorded as the user's own finding rather than a vendor or CISA signal. This changes the rating. The row was written on 06/11/2026 noting that the record carried no proof-of-concept signal at all, and a public PoC is a ๐ criterion under this report's rules, so it moves ๐ก โ ๐ . Exploitation is still unreported and the fix is still available ; what changed is that the flaw is now demonstrably reachable by anyoneTimeline
- 13/10/2026CVE record published (CVE List)
- 06/11/2026Microsoft Paint RCE fix exists โ but admins can't actually get it
- 06/11/2026Update โ Paint fix is rolling out, but the CVE record still doesn't match
- 10/11/2026Microsoft Paint RCE patch mix-up leaves fixed version unclear
Risk
7.0 High (v3.1, Microsoft CNA) โ CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C, temporal E:U/RL:O/RC:C (exploitation unproven, official fix), EPSS 0.734% (54.54th percentile, scored 05/11/2026, before the rescore). No ADP score (CWE-125 out-of-bounds read: Microsoft now describes it as letting an unauthorized attacker execute code locally, which fits the usual pattern for an image editor: the user opens a crafted file). Correction 19/11/2026: Microsoft revised the record on 10/11/2026. It previously read 8.1 High, AV:N/AC:H/PR:N/UI:N, with a description saying code could be executed over a network, which is why this row called the read-to-RCE pairing odd; the revised record is local with user interaction, so that oddity is gone
Fix
Yes โ 11.2609.401.0 or later (raised from 11.2605.91.0 when Microsoft revised the record on 10/11/2026, so a host updated to 11.2605.91.0 is still affected). The record names no KB number and no Windows build, which is consistent with an app update rather than a cumulative update, so check the installed Paint version on a sample host instead of assuming Windows Update covered it
Official description
Out-of-bounds read in Windows Paint allows an unauthorized attacker to execute code locally.
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
CWE-125