cve.bz

CVE-2026-83844 microsoft microsoft paint: Out-of-bounds Read

7.0 highEPSS 0.4%

High (7.0) in microsoft microsoft paint. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
Out-of-bounds read in Windows Paint allows an unauthorized attacker to execute code locally.

Severity

CVSS 3.1

7.0 high
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 33rd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-125 Out-of-bounds Read
Published
Modified
Assigned by
microsoft (CNA)
NVD analysis
Under analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-83844 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-83844?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-83844?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-83844 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • microsoft:microsoft paint

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft Paintfrom 11.0.0.0 before 11.2609.401.0

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • HackingLZ/CVE-2026-83844-public Harbor Check: matches CVE 1 star, C, created
    Out-of-bounds read in the legacy Microsoft Paint C2PA/JUMBF provenance parser (CVE-2026-83844): report, Paint reproducer, and reverse-engin…
  • LilPoule/CVE-2026-83844 3 stars, Python, created
    Microsoft Paint CVE-2026-83844 Verification Script
  • blkph0x/CVE-2026-83844_POC 1 star, Python, created
    Signed Paint A/B lab corroborating the publicly attributed CVE-2026-83844 C2PA CBOR read; scoped provenance side cases and evidence
  • zake1god/CVE-2026-83844 0 stars, PowerShell, created
    Safe CVE-2026-83844 Microsoft Paint host assessment and clearly separated synthetic shell lab
  • LACHHAB-Anas/CVE-2026-83844 0 stars, created
    Technical Exploitation Analysis of Paint2Shell CVE-2026-83844
3 more

Attack patterns (CAPEC)

  • CAPEC-540 Overread Buffers Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON