01 · The Real Story
A blindfolded restorer copying past the mural's edge — Paint reads outside the buffer and turns a malformed image into code execution
Microsoft Paint before 11.2605.91.0 contains an out-of-bounds read (CWE-125) when parsing malicious image files. An attacker who can deliver a crafted file and have it opened in Paint can trigger memory corruption that may lead to arbitrary code execution in the user's context.
Microsoft's HIGH 8.1 rating assumes a network vector with no user interaction. In practice, Paint is a desktop image editor, not a network-exposed service; the 'network' is just file delivery, and opening the file requires user action. The real risk is user-level code execution on a workstation with no high-value blast radius, so we downgrade to MEDIUM.
"Not a remote service—just a file parser that needs a click. No public exploit, no KEV, user-level code exec only."
02 · The Attack Path
4 steps from start to impact.
STEP 01
Craft malicious image file
Attacker creates a specially crafted image file (e.g., malformed BMP/PNG) that exploits the out-of-bounds read in Microsoft Paint's image parser. No public PoC exists, so this requires custom reverse engineering and exploit development.
Conditions required:
- Attacker knows target runs a vulnerable Microsoft Paint version
- Attacker can craft a file that reliably triggers the out-of-bounds read
Where this breaks in practice:
- No public exploit or PoC is available
- Exploit development required; AC:H applies
Detection/coverage: Static file analysis may flag malformed image headers; no known signatures exist.
STEP 02
Deliver file to target
Attacker delivers the malicious image file via phishing email, web download, shared folder, or removable media. The file must reach a user who will open it in Paint.
Conditions required:
- Target user can receive files from attacker
- Email gateway or browser filters do not block the file
Where this breaks in practice:
- Email gateways and browser Mark-of-the-Web warnings reduce delivery success
- File may be quarantined or blocked by endpoint protection
Detection/coverage: Email gateway, EDR, and browser reputation checks may inspect attachments.
STEP 03
User opens file in Microsoft Paint
The victim must explicitly open the crafted file in Microsoft Paint, either by double-clicking the file or selecting Paint as the application. This is the user-interaction step that the CVSS vector omits.
Conditions required:
- Microsoft Paint is installed and associated with the file type
- User chooses to open the file with Paint
Where this breaks in practice:
- Paint is not the default image handler for many file types on Windows 11
- User caution and security training reduce success
Detection/coverage: Endpoint detection may flag suspicious file opens, but Paint itself is a legitimate application.
STEP 04
Out-of-bounds read triggers code execution
When Paint parses the malformed file, it reads past the end of the buffer, corrupting memory and hijacking execution flow. The attacker gains arbitrary code execution in the context of the Paint process.
Conditions required:
- Vulnerable parser is reached with the crafted input
- Memory corruption leads to code execution despite OS mitigations
Where this breaks in practice:
- ASLR, DEP, CFG, and potential AppContainer sandbox for Store app complicate exploitation
- No evidence that the OOB read reliably leads to RCE in practice
Detection/coverage: Post-exploitation EDR may catch suspicious child processes or memory anomalies, but initial OOB read is not logged.
03 · Compensating Control
1
MEDIUM 5.8→IGNORE 0.0
SEVERITY REDUCEDApply the Microsoft Paint update to
11.2605.91.0 or later — Patch through Microsoft Store/Windows Update. Under noisgate remediation SLA for MEDIUM, complete within 365 days; no mitigation SLA applies, so go straight to remediation. This removes the vulnerable parser entirely.2
MEDIUM 5.8→IGNORE 0.0
SEVERITY REDUCEDUninstall or block Microsoft Paint for users who do not require it — Remove via app uninstall or use WDAC/AppLocker to restrict execution. This eliminates the attack surface; do it as a stopgap if you cannot patch quickly. Residual risk is none if Paint is unavailable.
3
MEDIUM 5.8→MEDIUM 5.8
Set default image handler to Photos or another viewer and block Paint association — Prevent accidental opening of crafted images in Paint; not a full control because Paint can still be launched manually, but reduces likelihood. Deploy within 30 days as a hardening measure.
What doesn't work
- Network firewalls and IPS: Paint is not a network service, so network-layer controls cannot block the attack.
- Email gateway file scanning: can reduce delivery but not block USB/web/cloud delivery; also no known signatures exist.
- ASR rules that block Office/child processes: irrelevant because Paint is invoked directly, not through Office macros.
04 · Intelligence Metadata
The supporting signals.
| In-the-wild status | No known exploitation; not in CISA KEV; VulDB reports no exploit exists. |
|---|---|
| Proof-of-concept availability | No public PoC; cve.tools and VulDB list no exploit; no GitHub repos named after CVE found. |
| EPSS score/percentile | 0.00734 (0.7%) / 50th percentile — low likelihood of exploitation in next 30 days. |
| KEV status | Not listed in CISA KEV as of 2026-10-13. |
| CVSS vector interpretation | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H; AV:N/UI:N overstate reality — file parsing is local and user-initiated. |
| Affected versions | Microsoft Paint 11.0.0.0 through <11.2605.91.0. |
| Fixed version | 11.2605.91.0 via Microsoft Store / Windows Update. |
| Scanning/exposure data | Not network-exposed; Shodan/Censys do not detect. Use endpoint inventory (MDE/SCCM) to find vulnerable Paint versions. |
| Disclosure date | 2026-10-13 (NVD published). |
| Reporting source | Microsoft Corporation (CNA); VulDB analysis. |
Sources.
05 · The Call
Final Verdict
↓ DOWNGRADED to MEDIUM (5.8/10)
Why this verdict
- User interaction is effectively required: despite
UI:N, Paint only processes files when opened by a user; the 'network' is file delivery, not a listening service. - No public PoC or in-the-wild exploitation: VulDB/cve.tools/Rapid7 report no exploit; EPSS 0.7% (50th percentile), not KEV.
- Role multiplier: Paint is a low-value workstation app; successful exploitation yields user-context code execution on a single endpoint, not domain/fleet/supply-chain impact.
- Post-exploitation constraints: modern Store app likely runs in AppContainer, limiting lateral movement and elevated actions.
Why not higher?
The CVSS AV:N/UI:N is misleading for a desktop image editor; a real attack chain requires a user to open a malicious file, and no exploit is public. The affected component has no high-value deployment role and the blast radius is a single user session.
Why not lower?
If exploited, the vulnerability still allows arbitrary code execution in the user's context on a widely installed Windows component, so the residual risk is not LOW/backlog; patch within the 365-day remediation window.
06 · Verification
Crowdsourced verification payload.
Run this on each Windows endpoint from an unelevated user session. Requires no admin rights; uses Get-AppxPackage to inspect the installed Microsoft Paint version. Example: powershell -ExecutionPolicy Bypass -File check_cve_2026_83844.ps1. Outputs VULNERABLE, PATCHED, or UNKNOWN. Exit codes: 0 patched, 1 vulnerable, 2 unknown.
# Check CVE-2026-83844 affected Microsoft Paint version
$ErrorActionPreference = 'Stop'
try {
$pkg = Get-AppxPackage -Name 'Microsoft.Paint*' -ErrorAction Stop | Sort-Object Version -Descending | Select-Object -First 1
if (-not $pkg) {
Write-Output 'UNKNOWN: Microsoft Paint package not found'
exit 2
}
$version = $pkg.Version
Write-Output ('Found Microsoft Paint version: {0}' -f $version)
$fixed = [version]'11.2605.91.0'
$current = [version]$version
if ($current -lt $fixed) {
Write-Output ('VULNERABLE: version {0} is below fixed version {1}' -f $version, $fixed)
exit 1
} else {
Write-Output ('PATCHED: version {0} is at or above fixed version' -f $version)
exit 0
}
} catch {
Write-Output ('UNKNOWN: ' + $_.Exception.Message)
exit 2
}