Latest news
Microsoft Paint has spent more than three decades as the app people open to crop a screenshot. Now it carries a CVE number. Patch deadlines have dominated the news cycle this week, and this one sits in a program most users never think of as software that needs maintenance. TechRadar covered the Windows Paint vulnerability under a blunt framing: update now. The underlying record is a Microsoft advisory for CVE-2026-83844, titled Windows Paint Remote Code Execution Vulnerability, published on October 13, 2026.
Microsoft’s own description is short. It says an out-of-bounds read in Windows Paint allows an unauthorized attacker to execute code over a network. Reporting based on the Microsoft and NVD description rates the flaw 8.1 out of 10 on the CVSS scale, which lands in the High band. The fix arrives through the Microsoft Store, not the regular Windows Update channel, and Microsoft-related reporting points to version 11.2609.401.0 or later as the corrected build.
The headline version of this story says attackers are already hitting Paint. The record does not support that yet. One report on the advisory specifically stated that there were no reports of exploitation in the wild. This article separates what Microsoft and the reporting actually confirm from what the louder headlines imply, then walks through the practical steps for checking and updating Paint on Windows 11. Along the way it covers why the delivery channel matters, what the bug class means, and what the case says about the shrinking gap between “harmless built-in app” and “attack surface.”
The Shattered Newsletter
The week’s biggest stories in tech, gaming and security, in one email.
Free, once a week. Unsubscribe any time.
Don't miss new tech stories on Google
Add Shattered once in the Google app and our stories show up in your news suggestions.
Microsoft published its security advisory on October 13, 2026. The product is Windows Paint, and reports identify it as the Paint app that ships with Windows 11. The weakness is listed as a remote code execution vulnerability, tracked as CVE-2026-83844. The advisory text reads: “Out-of-bounds read in Windows Paint allows an unauthorized attacker to execute code over a network.”
Three phrases in that sentence carry the weight. “Out-of-bounds read” names the bug class. “Unauthorized attacker” means the person exploiting it does not need an account or elevated rights on the target. “Over a network” points to the attack vector, which is the part that pushes the score up. A bug that required local access to the machine would normally score lower than one reachable across a network.
The score reported from the Microsoft and NVD description is 8.1 out of 10. That is High, not Critical. The gap matters for triage. Critical ratings usually cover flaws that need no user interaction and have trivial attack complexity. An 8.1 often signals that some condition has to line up, such as a user opening a crafted file or an attacker needing specific timing. The advisory text available does not spell out those conditions, so this article does not guess at them.
Since the advisory went live on October 13, 25 days have passed as of November 7. For a consumer app delivered through a store, that is plenty of time for the fixed build to have reached most machines with automatic app updates switched on. It is also long enough for a lazy attacker to build tooling from a diff of the old and new versions, which is why the “update now” advice carries weight even without confirmed attacks.
The table below collects every specific that the advisory and the reporting support. Anything outside this table should be treated as context or analysis, not as a confirmed fact about this bug.
Notice what the table leaves out. There is no confirmed exploit count, no named threat actor, and no public proof-of-concept referenced in the sources behind this story. Those blanks are deliberate. Filling them with plausible-sounding detail is how a modest patch notice turns into a panic cycle.
An out-of-bounds read happens when a program reads memory beyond the buffer it was meant to use. In a drawing program, the buffer might hold pixel data, layer metadata, or fields from an image header. If a file claims its image is larger than the data it actually contains, naive parsing code can walk past the end of the allocation.
Reads sound harmless compared with writes. In practice, they often are not. A read past a buffer can leak pointers, which defeats address randomization. It can also return attacker-influenced values that the program later uses as a length, an index, or a function pointer. Chain a leak with a second weakness and a read bug becomes the first link in a code execution chain. Microsoft classified this one as remote code execution, so its analysts saw a route from the read to running code. The public text does not describe that route.
A network attack vector in the CVSS system does not mean Paint listens on a port like a web server. Paint is a desktop app, so the realistic path involves content that arrives over the network and gets opened or parsed by Paint. Think of an image sent by email, fetched from a shared drive, or handed over through a link. The vector rating describes where the attacker sits relative to the target, not how the app is wired.
One claim circulating in social posts calls the flaw “zero-click.” The Microsoft advisory text available does not establish that. It confirms network-based code execution and nothing more specific about user interaction. Readers should treat the zero-click label as unconfirmed until Microsoft or another named source documents it.
The story as TechRadar framed it urges users to update, and the broader chatter says Paint is under attack. The documented picture is narrower. One report on the advisory stated there were no reports of exploitation in the wild. That is the most conservative reading and the one this article follows. No source in the verified record names a campaign, a malware family, or a victim.
This split is not hair-splitting. Defenders prioritize by exploitation status. A High-rated bug with no known attacks goes into the normal patch cycle with a short deadline. A bug on an active-exploitation list gets emergency treatment. Mislabeling the first as the second burns trust, and trust is what gets people to apply the next real emergency patch.
The detail that surprises many Windows users is the delivery path. Microsoft distributed the Paint fix through the Microsoft Store, according to reporting on the advisory, rather than through the monthly Windows Update mechanism. Paint on Windows 11 is a packaged app, so Microsoft can update it on its own schedule, separate from the operating system.
That model has a clear upside. A security fix for a single app does not need to wait for a cumulative OS update, a reboot window, or a testing ring built for kernel changes. Microsoft can push a corrected package and let the Store handle it. The downside is just as clear. Anyone who has disabled automatic Store updates, runs a locked-down image, or blocks the Store on managed machines will not receive the fix through the path they watch most closely.
Security teams often monitor Windows Update compliance dashboards and call it done. A Store-delivered fix slips through that net. If an organization uses patch reports that only track OS-level updates, the Paint flaw can sit open and nobody sees it on the dashboard. This is a recurring operational blind spot for packaged inbox apps, and the Paint advisory is a clean example of it.
The fastest manual route runs through the Store. Open the Microsoft Store, go to the Library section, and choose to get updates. Paint should update if it is behind. Then open Paint, go to its settings or about screen, and confirm the version number. The reported corrected build is 11.2609.401.0 or later.
For a scriptable check, PowerShell can read the installed package version directly. Run it in a normal user session:
Compare the returned version against 11.2609.401.0. If the number is lower, the machine still runs a build from before the reported fix. To trigger an update from the command line, the Windows Package Manager can list pending Store upgrades:
If Paint appears in the output, run the upgrade for it. If the Store is blocked by policy, the update will not arrive and an administrator has to handle it through whatever distribution tool the organization uses. Either way, record the version before and after so there is evidence the fix landed.
Not every report agrees on the build that counts as protected. Microsoft-related reporting identifies 11.2609.401.0 or later. A different number, 11.2605.91.0, has also appeared in coverage as the current protected build. The two cannot both be the cutoff, because the second is a lower version.
The conservative approach is to use the higher figure. If a machine reports 11.2609.401.0 or newer, it clears both claims. If it reports something between the two numbers, it is ambiguous and should be updated further. This follows the same rule that any careful defender applies when sources disagree on a fix threshold: take the strictest requirement and move on.
Version drift like this is common with Store-distributed software. Packages roll out in stages by region and device, so different outlets can observe different “latest” builds on the same day. The Microsoft advisory page is the document to check for the authoritative fixed version, and administrators should verify it there before documenting compliance.
For a managed fleet, the response splits into inventory, enforcement, and verification. Inventory means finding out which machines run Windows 11 with the packaged Paint app and what version each one reports. Enforcement means making sure the Store update path is open, or pushing the package through the organization’s own management tooling. Verification means re-running the version query and logging the result.
Smaller teams without a dedicated security staff can lean on scanning tools to catch gaps like this one. Our roundup of vulnerability scanners for teams of one to three people covers options that flag outdated software without a big setup cost. The caveat is that scanners differ in how well they see Store-packaged apps. Test the tool against a known out-of-date Paint install before trusting a clean report.
Where policy allows it, consider whether the machine needs Paint at all. On servers and kiosk images, an unused drawing app is pure risk with no payoff. Removing it shrinks the attack surface more reliably than any patch cadence. On general desktops, removal is less practical, so patching and user training on unexpected image files remain the main controls.
This story sits in the coding-tools cluster for a reason. Developer workstations are full of tools that parse untrusted content, from image viewers to editors to terminals. Engineers also receive screenshots, mockups, and design exports all day. A flaw in a basic image tool is a plausible entry point onto a machine that holds source code, signing keys, and cloud credentials.
The same logic applies to the newer class of AI-assisted tools that read files and call external servers. Auditing which Cursor MCP servers have access to your environment follows the same discipline as auditing Paint: know what runs, know what it can touch, and know how it gets updated. The pattern is identical even though the products look nothing alike.
For engineering managers, one practical move is to add packaged inbox apps to the software inventory used for vulnerability tracking. Many inventories list only installed programs from traditional installers and miss Store packages entirely. Teams that already generate software bills of materials for their own products can extend the habit to the workstation fleet. A Dependency-Track setup for CycloneDX SBOMs shows the product-side version of that workflow.
Attackers have long targeted parsers. File format handlers for images, documents, fonts, and media have produced a steady stream of memory safety bugs across every major platform, because the formats are complex and the code that reads them often dates back decades. Paint fits the pattern. It opens many image types, and each type needs its own parsing logic.
What changed over the last several years is the delivery model. Microsoft moved a growing set of inbox apps, including Paint, Notepad, and others, into packaged form so they can update independently of the operating system. That shift speeds fixes. It also created a two-track patch world in which a Windows machine can be fully current on cumulative updates and still run a vulnerable inbox app.
Memory safety bugs are not unique to Microsoft. A recent musl and OpenSSH password bypass shows the same family of problem on Linux, where an input length edge case led to an authentication failure. Different platform, different component, same root cause: code that trusts a length it should have checked.
The table below compares the three common ways a Windows 11 app update reaches a machine. It describes general behavior of the channels, not figures specific to this advisory.
The practical lesson is that “fully patched” now means two checks, not one. OS-level compliance tells you about the operating system. App-level compliance tells you about the Store packages. Teams that report only the first number are guessing about the second.
A single Paint advisory will not move markets. Nothing in the record suggests a campaign large enough to hit earnings, and no source ties the flaw to any named incident. The wider effect is on how vendors and customers think about inbox software. Each advisory for a basic bundled app strengthens the argument that every shipped component needs an owner, a patch plan, and a way to report its version.
Security vendors have an obvious incentive to amplify stories like this one, because “even Paint” is a memorable pitch for endpoint tools. Readers should weigh that incentive when a headline implies active attacks. The honest summary is that the bug is real, the rating is High, the fix exists, and the exploitation claim is unproven in the sources reviewed here.
For Microsoft, the cost is reputational and operational. The company keeps expanding what ships in Windows 11, and each added component adds code to maintain. The Store delivery path lets it respond fast, which is a strength. Yet it also means customers must trust and monitor a second update system. Enterprises that built their patch process around the monthly OS cycle now carry extra work.
Other vendors face the same trade. Any platform that bundles viewers and editors takes on the burden of keeping them current. Browser makers solved this years ago with silent background updates. Desktop OS vendors are catching up, and the Paint case shows the gaps that remain on the way.
These are analysis, not reporting. They reflect where the evidence points, and each could prove wrong.
Three signals will settle the open questions. First, whether Microsoft updates its advisory to flag exploitation, which would move this from routine to urgent. Second, whether a government vulnerability catalog adds the CVE, a step that usually follows confirmed attacks. Third, whether independent researchers publish a technical write-up that clarifies the user interaction needed, which would settle the zero-click claim one way or the other.
Until then, the guidance holds steady. Check the Paint version, confirm it reads 11.2609.401.0 or later, and make sure the Store update path is working on every Windows 11 machine you manage. The effort takes minutes per device, and it closes a path that Microsoft itself rated High.
For more coverage of developer and software tooling, see our software section.
It is the identifier for the Windows Paint Remote Code Execution Vulnerability that Microsoft published in an advisory on October 13, 2026. Microsoft describes it as an out-of-bounds read in Windows Paint that lets an unauthorized attacker execute code over a network.
Reporting based on the Microsoft and NVD description gives it a CVSS score of 8.1 out of 10, which falls in the High category. That is serious but below the Critical tier.
That is not confirmed. One report on the advisory said there were no reports of exploitation in the wild. Headlines suggesting active attacks go beyond what the available sources document.
Microsoft shipped the fix through the Microsoft Store, not Windows Update. Open the Store, go to the Library, and check for updates. Then confirm the Paint version is 11.2609.401.0 or later, which is the corrected build in Microsoft-related reporting.
Paint on Windows 11 is a packaged app that updates independently of the operating system. According to reporting on the advisory, Microsoft used that Store path for the fix, so a machine can be current on Windows Update and still carry an old Paint build.
Not established. The Microsoft advisory text confirms code execution over a network but does not say whether the user must open a file or take another action. Treat the zero-click label as unconfirmed.
Reports conflict. Microsoft-related coverage names 11.2609.401.0 or later, while another figure, 11.2605.91.0, has also appeared. Use the higher build as your target and check the Microsoft advisory for the authoritative number.
The Shattered Newsletter
The week’s biggest stories in tech, gaming and security, in one email.
Free, once a week. Unsubscribe any time.
Ryan Cole writes about security engineering and protocols: how HTTPS, certificates, and modern encryption protect data in transit, explained without the jargon.
Independent explainers on cryptography, security, privacy and the technology behind provably-fair systems. Home of the original SHA-1 collision research.
The Shattered Newsletter: the week’s biggest stories in tech, gaming and security.
About the Author
