Our scanner flagged CVE-2026-83844 as high severity in Microsoft Paint. I've seen conflicting reports about whether a fixed version is available. How are you assessing the risk and handling it in the meantime?
What are you doing about the Paint CVE while the update is hard to find?
Answers
Check Microsoft's security update guidance against the Paint version actually installed, then see what your Store update channel offers. Paint is distributed as a Store app, so a regular Windows patch check may not tell you whether the app is current.
The reports about the fixed build and its availability don't all agree. Treat the version in the current Microsoft guidance as the target rather than assuming the newest build you can download is fixed. Once it's available, deploy it through your app update process and rescan.
Reply to this answer
If Paint isn't needed on a group of machines, uninstalling it is a reasonable temporary option. Check for users or workflows that depend on it first, and verify removal before closing the scanner finding.
Reply to this answer
I wouldn't read the high score as the whole story. Check Microsoft's current description for the attack requirements, then look at which devices have the affected version and how those devices are exposed.
A network attack vector alone doesn't establish that Paint is listening directly on the internet, or that a router makes the issue harmless. The reports differ on user interaction too, so I'd verify that detail rather than build the risk assessment around either assumption.
Reply to this answer
Don't assume ordinary image handling always opens Paint. Check file associations and actual usage in your environment, especially for formats associated with Paint, when deciding which users and machines need attention first.
Reply to this answer
Add your answer
Answers are reviewed before publication.
6j~sprocketfinch_384:
Availability may differ by region or update channel, so it's worth checking on the affected devices rather than just one test machine.