Re:MS Paint Remote Code Execution Vulnerability
by dboreham on Thursday November 05, 2026 @04:06PM
(#50384456)
Presumably this is like many other graphics tool vulnerabilities this works by the attacker persuading a user to open a file that exercises the bug. Not terribly unusual.
Re:MS Paint Remote Code Execution Vulnerability
by 80fj0348i on Thursday November 05, 2026 @05:34PM
(#50385475)
I'm no expert but so much of Windows is implemented as services. svchost.exe is probably involved somehow. Like it wouldn't surprise me if Copilot is implemented as a service and it talks to Paint via IPC messages or something
Re:MS Paint Remote Code Execution Vulnerability
by 80fj0348i on Thursday November 05, 2026 @08:02PM
(#50386849)
It would make sense that it could listen for messages like "your generated image is ready!" and pass bitmap data to Paint. And media like images are a common source of vulnerabilities since you're basically passing binary data into the software.
Re:MS Paint Remote Code Execution Vulnerability
by knottn on Thursday November 05, 2026 @05:41PM
(#50385544)
Not to imply any particular comparison to less serious websites where the karma system over time may have resulted in a disproportionate surplus of one liner jokes and other spammy low quality posts.
Re:MS Paint Remote Code Execution Vulnerability
by Sohcahtoa82 on Thursday November 05, 2026 @07:29PM
(#50386579)
This site absolutely does jokes, it just doesn't beat horses into bloody pulps with the jokes the way reddit does. We have a higher standard. A joke has to actually be funny, and not some tired reference.
Re:MS Paint Remote Code Execution Vulnerability
by VorpalWay on Thursday November 05, 2026 @04:14PM
(#50384542)
I'm thankfully out of the loop on Windows these days, but as I remember it Paint did not have any network features? Is that still true? If if is, maybe it is a misfiling of the CVE and it isn't remote?
Or are they chaining a browser auto opening a download in paint, (but browsers shouldn't do that)...
Re:MS Paint Remote Code Execution Vulnerability
by radicalbyte on Thursday November 05, 2026 @04:48PM
(#50384927)
Why for the love of everything that is good does MS Paint have network trash in it. It's a super simple bitmap editor. Like Notepad, it's simple and just works.
Make a new product and bundle that as an option if you want to drastically change the functionality.
Re:MS Paint Remote Code Execution Vulnerability
by waz0wski on Thursday November 05, 2026 @04:50PM
(#50384959)
Hate to break it to you..
> Notepad in Windows includes AI features powered by Copilot that help refine and shorten text with the assistance of GPT. By default, these AI features are enabled on managed devices
Re:MS Paint Remote Code Execution Vulnerability
by gregschlom on Thursday November 05, 2026 @04:15PM
(#50384544)
"An unauthenticated attacker could exploit this vulnerability by sending a specially crafted packet to an affected service over the network. Successful exploitation could allow the attacker to execute code on the target system. No authentication or user interaction is required.."
Re:MS Paint Remote Code Execution Vulnerability
by jdiff on Thursday November 05, 2026 @07:51PM
(#50386758)
Yeah, OpenCVE also includes this:
> After applying the update, verify that the target Windows systems are running a version that includes the CVE fix before disabling legacy file‑open processing in Paint.
Which is complete nonsense. "Legacy file-open processing" isn't a real configurable option in Paint and this seems to suggest that enabling it is some sort of mitigation. The resolution is simply to update Paint.
Re:MS Paint Remote Code Execution Vulnerability
by IanCal on Thursday November 05, 2026 @04:22PM
(#50384625)
It mentions that it may rely on other services or security measures running- I wonder if there’s something like this hitting a firewall or av and then that calling out to paint to check file type or size out something like that?
Re:MS Paint Remote Code Execution Vulnerability
by Den_VR on Thursday November 05, 2026 @04:25PM
(#50384665)
The direct implication is that current generations of ms paint are a “service over the network.” Probably a theoretically possible RPC end point of svchost.exe
Re:MS Paint Remote Code Execution Vulnerability
by jdiff on Thursday November 05, 2026 @11:34PM
(#50388249)
But why MS Paint? What functionality does it offer to another program to get called on specifically? And if this other service isn't calling on it specifically, what else can it be tricked into calling? And how many of those are also vulnerable to being stabbed in the back? The smaller interior holes are a problem, sure, but it seems like the CVE should be for the hull hole in that case.
Re:MS Paint Remote Code Execution Vulnerability
by TZubiri on Thursday November 05, 2026 @04:34PM
(#50384763)
Maybe because a .bmp file could be sent remotely.
Or maybe after the .bmp file is executed, it can install something that opens an outbound TCP connection to its C2, and thus can receive commands. Would not need admin privileges because it doesn't open a port, just 'outbound' connections, like a long-poll.
Re:MS Paint Remote Code Execution Vulnerability
by TZubiri on Thursday November 05, 2026 @09:05PM
(#50387245)
you are right, it seems like the latter outbouns tcp connection is already being opened by paint, and that is what is exploitable.
since it exposes no port, I’d assume it isn’t trivial to exploit, paint will chose its target (a microsoft domain or IP), the exploit must involve some error in destination selection, or simply allowing a mitm to impersonate microsoft.
this is inline with Attack Complexity High, attacker needs to be either in the network path (mitm) or control the erroneous destination of the connection (say mircosoft.com), possibly blocking (dosing) the higher priority genuine destination
Re:MS Paint Remote Code Execution Vulnerability
by jdiff on Thursday November 05, 2026 @10:05PM
(#50387651)
Seems odd even for a vibecoded copilot integration to make repeated, unprompted network requests. And if they're not repeated and unprompted, then we don't meet the "no user input" requirement.
Re:MS Paint Remote Code Execution Vulnerability
by Sohcahtoa82 on Thursday November 05, 2026 @04:45PM
(#50384897)
Because the definition of "remote" has been expanded in the name of resume-driven development to include sending a malicious file that a victim has to open.
Re:MS Paint Remote Code Execution Vulnerability
by 6thbit on Thursday November 05, 2026 @06:43PM
(#50386203)
I wonder if it could be through a file:// or some deeplink custom url handler that opens in Paint and clicking on it with some carefully crafted file path could make it read out of bounds (since that's the associated weakness reported) and execute something.
Re:MS Paint Remote Code Execution Vulnerability
by jdiff on Thursday November 05, 2026 @06:48PM
(#50386248)
Whatever it is, it doesn't require any clicking or user interaction. Maybe my imagination is just limited but I can't imagine why Paint is making itself available for incoming traffic on the network.
Re:MS Paint Remote Code Execution Vulnerability
by jdiff on Thursday November 05, 2026 @10:54PM
(#50387954)
Mine doesn't have a mouse or keyboard at the moment, so I'm only checking over an SSH->WSL connection. But it sure doesn't look like it's opening any ports from here.
So I guess either some random OS component is listening to the network and just-as-inexplicably asking Paint to do something for it. Or one of Paint's outbound connections is vulnerable if hijacked by a mitm. Network interception's one of the examples used for the "High" Attack Complexity rating that MS gave this CVE. Maybe powered by eMudhra for any systems that haven't revoked those certs? That'd be topical.
Re:MS Paint Remote Code Execution Vulnerability
by Arainach on Thursday November 05, 2026 @06:15PM
(#50385917)
MSRC[1] says otherwise:
> An unauthenticated attacker could exploit this vulnerability by sending a specially crafted packet to an affected service over the network. Successful exploitation could allow the attacker to execute code on the target system. No authentication or user interaction is required.
Re:MS Paint Remote Code Execution Vulnerability
by Arainach on Friday November 06, 2026 @12:38PM
(#50395571)
It's bizarre that you're doubling down in the face of statements from Microsoft's security experts who have the full context of the investigation and the source code. It's worth some self-reflection on what drove you to make this post.
Re:MS Paint Remote Code Execution Vulnerability
by Arainach on Friday November 06, 2026 @02:20PM
(#50397034)
It says that "no user interaction is required", so phishing is explicitly not what this vulnerability is about.
You haven't declared any privileged knowledge of this attack or MS Paint and have, on vibes, doubled down on what you assume must be going on despite other evidence.
Re:MS Paint Remote Code Execution Vulnerability
by Arainach on Friday November 06, 2026 @05:38PM
(#50399446)
> Maybe you should self-reflect on why you are offended by my comment
A significant chunk of the world's problems today are caused by or exacerbated by people who confidently assert things they believe regardless of what evidence or experts say, and who dismiss expertise. Those people are emboldened by others allowing them to spew nonsense unchecked, and I have no interest in seeing HN degraded similarly.
You're moving goalposts. A commenter asked what Networking MS Paint had in the context of this vulnerability. You made an assertion not supported by the documentation we had, and now you're trying to claim that there could be other vulnerabilities rather than admitting that you made a mistake without doing any research.
Re:MS Paint Remote Code Execution Vulnerability
by decidu0us9034 on Friday November 06, 2026 @01:39PM
(#50396445)
The boilerplate FAQ text is frequently wrong or incomplete. You can go through the catalog and look through some of them and see how many have multiple revisions. I think, if you want to know definitively, you have to patch diff it
Re:MS Paint Remote Code Execution Vulnerability
by onei on Friday November 06, 2026 @05:15AM
(#50390478)
Some years ago, I ended up on a call with a support team guy, helping him under some parts of a system I worked on. He shared his screen, started drawing diagrams. It took me a whole 10 minutes to realise it was in paint, he was just that good at using it.
Turns out paint was the thing almost every customer had installed/had access to, so he worked to the lowest common denominator and got really good at using it. I guess now he'll need to find a new tool to astonish devs with.
Re:MS Paint Remote Code Execution Vulnerability
by ethbr1 on Friday November 06, 2026 @06:55AM
(#50391289)
If you're in support across multiple customers, especially in regulated industries, you learn to rely on the minimum common denominator, which usually means OS utils.
And at the end of the day $2 and $2000 screwdrivers are both still screwdrivers.
Re:MS Paint Remote Code Execution Vulnerability
by joshspankit on Friday November 06, 2026 @09:46AM
(#50392948)
Before MS, there was a time where it wasn’t possible to get a virus by receiving an email. Users had to click on the attachment. Email itself is a text protocol after all.
Then they added automatic HTML parsing of incoming emails, and the attackers cheered.
Re:MS Paint Remote Code Execution Vulnerability
by pjmlp on Friday November 06, 2026 @03:40AM
(#50389719)
They supposedly did, that is why most stuff on Azure is now a mix of Java, C#, Go and Rust with very little C and C++.
And there is the SFI program.
However this is a Windows application, and in spite some Rust advances in WinDev, it is pretty much C and C++ turf, with Rust getting the same warm reception as .NET used to enjoy.
Guess which language is Paint written on?
Nontheless, they are doubling down on sandboxing Windows, macOS, iOS and Android style, for quite some time, exactly to become security first as you are asking for.
Re:MS Paint Remote Code Execution Vulnerability
by everylostbit on Thursday November 05, 2026 @05:20PM
(#50385308)
This seems to affect only paint 11.0.0.0 up to, but not including, 11.2605.91.0.
For folks like me, running a much older version, its probably safe, although its Windows so, I'm not too sure.
Re:MS Paint Remote Code Execution Vulnerability
by everylostbit on Thursday November 05, 2026 @07:23PM
(#50386533)
yes that is my exact situation. I think (hope?) Microsoft would've disclosed it if prior versions were affected too, although I never heard the "old" paint have anything to do with network, so there's that.
Re:MS Paint Remote Code Execution Vulnerability
by chungy on Thursday November 05, 2026 @10:37PM
(#50387847)
Windows 7 added ribbons to the UI. It's unlikely it was a rewrite. Just a retooling of what Vista had, which in turn what Windows XP had, which... [continue down the line until Windows 1.0].
Re:MS Paint Remote Code Execution Vulnerability
by echion on Thursday November 05, 2026 @11:04PM
(#50388024)
Reminds me of Zawinski's Law of Software Envelopment[^1,2]: "Every program attempts to expand until it can read mail. Those programs which cannot so expand are replaced by ones which can."
Re:MS Paint Remote Code Execution Vulnerability
by QuantumNomad_ on Friday November 06, 2026 @02:12AM
(#50389156)
I remember when I was doing pixel art, there were some purists that insisted that using layers and transparency/opacity to create windows for your buildings is more or less cheating. According to them, one should manually figure out what the color palette should be for things seen through a window.
Anyway, I continued using layers and transparency/opacity. Pixel art was hard enough already for me, so I didn’t feel that it made sense to artificially make it even more difficult for myself at the time. I had enough other aspects of pixel art to work out already in order to try to get better at it.
Re:MS Paint Remote Code Execution Vulnerability
by Measter on Friday November 06, 2026 @01:52PM
(#50396630)
I can't reproduce any of those issues. When drawing the indicator snaps to a pixel, so it's perfectly clear where it's going. When I draw a line, it's pixel-perfect when moving the control points, likewise after it finalises. And when I copy a section of the image and paste it back in, it's pixel-perfect as I move and when I finalise. There doesn't seem to be a true resize; all I seem to be able to do is change the size of the canvas, which doesn't add any kind of aliasing.
But I've only used the program for less than 5 minutes, so maybe it's configured differently?
Re:MS Paint Remote Code Execution Vulnerability
by jasomill on Friday November 06, 2026 @03:46PM
(#50398273)
And create single-pixel images. My most used application of Paint by far is creating single-pixel PNG files to work around the fact that "solid color" is not an option for lock/login screen backgrounds.
Re:MS Paint Remote Code Execution Vulnerability
by mihaaly on Friday November 06, 2026 @08:04AM
(#50391844)
I hope MS is not getting exclusive right for manufacturing spoons because I want mine to scoop up stuff like soup or ice-cream without smart features activated by elegant touch UI on the handle like cutting down trees being in the way to the grocery store to 'elevate user experience', or others. This stuffing more and more into everything and anything for the sake of shock and awe is a stupid (and dangerous) thing.
Re:MS Paint Remote Code Execution Vulnerability
by JdeBP on Thursday November 05, 2026 @09:53PM
(#50387573)
You haven't spotted that it's regularly being released the month following the revision number. (-: Because Microsoft will of course have a release pipeline that things have to go through.
They're not a positional notation. It's version 11.2605.91 recently. It was 11.2605.81 earlier this year. There was an 11.2605.71 and an 11.2605.61 before that. Last year, there was a 11.2504.451 . The year before there was a 11.2402.32 .
Microsoft's versioning systems are not 4 columns where a tick around of one increments the one before it. The easiest way to think of them is madness made for marketing purposes. (Windows NT starting at 3.1, for example.) There is some logic to it, but nowadays it's often four entirely different things jammed together, ticking around independently. Like the version of Windows, the year and month of the release, and perhaps a daily build number or some such.
Windows NT itself has a monotonically increasing build number as part of its versioning that started some time in 1992 and is currently just over 26 thousand.
Re:MS Paint Remote Code Execution Vulnerability
by grishka on Friday November 06, 2026 @04:22AM
(#50390080)
You can't have finished software any more. It's now illegal or something. Must keep changing things forever. And must add some AI features of course, to make the VCs happy.
Re:MS Paint Remote Code Execution Vulnerability
by jdiff on Thursday November 05, 2026 @06:30PM
(#50386067)
Doesn't seem to be:
> An unauthenticated attacker could exploit this vulnerability by sending a specially crafted packet to an affected service over the network. Successful exploitation could allow the attacker to execute code on the target system. No authentication or user interaction is required.
Re:MS Paint Remote Code Execution Vulnerability
by gadrev on Thursday November 05, 2026 @07:27PM
(#50386567)
Did the same and it quickly updated itself when I went into the "Paint" page (but I had to go there first). No indication of what just happened a few seconds later.
Re:MS Paint Remote Code Execution Vulnerability
by ManuelKiessling on Thursday November 05, 2026 @07:48PM
(#50386737)
For a split second, I visualized you walking into a brick and mortar Microsoft Store to get your security update done on your laptop, and somewhere in the middle of that split second I caught myself thinking „typical Microsoft“, and then I came to my senses.
Re:MS Paint Remote Code Execution Vulnerability
by izacus on Friday November 06, 2026 @02:50AM
(#50389381)
What kind of nonsense are you writing here right now? When the next Linux kernel CVE happens, you'll also delete all the kernels from your fleete because they're a malicious backdoor?
When did y'all stop using some basic sense before writing? -_-
Re:MS Paint Remote Code Execution Vulnerability
by pjmlp on Friday November 06, 2026 @03:43AM
(#50389747)
Windows Update and Store are slowly becoming the same, and Paint gets delivered via the store for quite some time, there was even some drama related to it.
Re:MS Paint Remote Code Execution Vulnerability
by speedstyle on Friday November 06, 2026 @09:27AM
(#50392677)
At the moment I just use Zed, or I imagine I'd be fine with Sublime. When I used Jetbrains/VSCode, I would grab Notepad/Notepad++ when I didn't want to wait for them to open, set up a project, etc. But if something 'heavyweight' is quicker than notepad, and the features don't get in my way, I don't need anything else. In fact I still appreciate the extra functionality with those one-off text/data/scripts - format, regex replace, diff, occasionally even LSP like shellcheck
Re:MS Paint Remote Code Execution Vulnerability
by amluto on Thursday November 05, 2026 @07:41PM
(#50386686)
mspaint.exe is quite likely to have at least one code execution vulnerability if one opens a malicious file, but I bet it's very safe against remote attack :)
Re:MS Paint Remote Code Execution Vulnerability
by mattstir on Friday November 06, 2026 @08:47AM
(#50392246)
Presumably as part of the generative AI stuff they crammed into it? They've been hilariously cagey about the details here which makes me think it has to be AI-feature related
Re:MS Paint Remote Code Execution Vulnerability
by sigmar on Friday November 06, 2026 @09:26AM
(#50392666)
Not sure what you think is "hilariously cagey", but why would they only be "cagey" if the bug was from ai-features?
Also it says paint versions are "affected from 11.0.0.0 before 11.2605.91.0" which I take to mean the bug has been there since Windows 11 was released in 2021
Re:MS Paint Remote Code Execution Vulnerability
by 6thbit on Thursday November 05, 2026 @07:12PM
(#50386446)
I'm just in full denial that paint runs a server. Happy to be corrected if someone has a windows machine handy to verify.
But From [0]:
> A total of 59 of the October CVEs fit my definition of wormable. Specifically, 57 contain both “An unauthenticated attacker could exploit this vulnerability by sending a specially crafted packet to an affected service over the network” and “No authentication or user interaction is required.”
Makes you wonder if MS is just copy-pasting boilerplate on CVEs and disclosed incorrectly the scope of the one in Paint because they had 56 other bugs to disclose.
So I'm not discounting reporting human error here, yet.
Re:MS Paint Remote Code Execution Vulnerability
by xlayn on Thursday November 05, 2026 @07:27PM
(#50386560)
WHY ON HELL paint has a remote code execution in the name of God?
WHY? is this because someone who needs to build a CV decided to network something on ..... I can't come with a reason why "An unauthenticated attacker could exploit this vulnerability by sending a specially crafted packet to an affected service over the network." will cause paint to start being nice to an attacker and leaking crypto secrets etc.. the thing says sending a specially crafted packet.. this means windows is part of the attack vector, but that just makes the WHY bigger, really, why?
Re:MS Paint Remote Code Execution Vulnerability
by dathinab on Thursday November 05, 2026 @07:57PM
(#50386812)
unlikely
IFF there is a NSA backdoor it likely would be:
- not in paint, but something you can't disable/remove in hardened special purpose windows setups
- not be easily usable by 3rd parties, like some auth accidentally accepting some quite specific other password (e.g. due to some bug reading the expected hash from the wrong place) or similar
lets not forget as much as the NSA might want to spy on you they also want to keep China/Russia out of spying on US companies. A traditional RCE in paint is very counter productive for that.
Re:MS Paint Remote Code Execution Vulnerability
by BowBun on Thursday November 05, 2026 @08:50PM
(#50387143)
unless they actively work with MS to keep their backdoor fresh, one can reasonably assume a potential backdoor _was_ well-hidden and advanced for the time period when it was introduced. What about after 20 years and LLMs decompiling everything?
Re:MS Paint Remote Code Execution Vulnerability
by ranger_danger on Friday November 06, 2026 @01:13AM
(#50388791)
They (and other governments) can do multiple things at the same time.
One one hand they can actively try to work with companies to get secret back doors put in, sure. But I imagine that's not usually very successful. Lavabit chose to go out of business instead of doing so... I wonder who else is out there that we don't know about.
But we also have evidence that they actively look for, buy, and hoard, unknown (to the vendor) exploits for their own possible later use in case they need it for something.
I'm sure you can imagine that it's much more advantageous to keep collecting all kinds of different ways to get into a system in case one method is not applicable for any number of reasons.
Re:MS Paint Remote Code Execution Vulnerability
by goodcitizen on Friday November 06, 2026 @06:32AM
(#50391069)
I believe they're already quite happy with the Windows OS itself for this purpose, and probably some other firmware-level rootkits across many products like Intel and Qualcomm chipsets. Their contracts with Meta might be helpful too.
Re:MS Paint Remote Code Execution Vulnerability
by gruez on Thursday November 05, 2026 @08:26PM
(#50387002)
>I can't come with a reason why "An unauthenticated attacker could exploit this vulnerability by sending a specially crafted packet to an affected service over the network."
The Microsoft link doesn't mention this at all, so my guess it's "remote" in the sense that a zip file exploit is "remote"
Re:MS Paint Remote Code Execution Vulnerability
by jdiff on Thursday November 05, 2026 @10:07PM
(#50387672)
Remote, and inapplicable. One of the very few things the Microsoft link does mention that no user interaction is required. A banana left out in the walkway still requires the user to go for a walk.
> How could an attacker exploit this vulnerability?
> An unauthenticated attacker could exploit this vulnerability by sending a specially crafted packet to an affected service over the network. Successful exploitation could allow the attacker to execute code on the target system. No authentication or user interaction is required..
Re:MS Paint Remote Code Execution Vulnerability
by augment_me on Thursday November 05, 2026 @09:01PM
(#50387217)
Any extraction of behavioural surplus is a win, Nadella went hard on this in Windows 11. If you are drawing something for your child in paint, you might want to buy pampers or something.
Re:MS Paint Remote Code Execution Vulnerability
by IFC_LLC on Thursday November 05, 2026 @07:52PM
(#50386774)
At this point I want to declare that air-gapped network with the transfer only over USB drives is a viable and valuable method of handling IT security. Outside transfer only happens by people manually copying text onto a floppy and reading it from a floppy.
Re:MS Paint Remote Code Execution Vulnerability
by logicallee on Thursday November 05, 2026 @07:58PM
(#50386822)
There's no remote code execution vulnerability in Paint. What was going on is that yesterday I put together a prospectus for a $20 stock offering[1] and as part of this I used paint while I created ascii art for the prospectus[2]. A defense contractor is scare mongering that this is somehow a remote code execution vulnerability, probably to sell defense services. As you can see, the cve doesn't contain any actual vulnerability. Paint doesn't have any network code at all. Nor buffer overflows. It's very simple bitmap graphics and was carefully tested. It's a 917 kb binary that has been static tested for 20 years.
However, the scare mongering caused my posts to be soft locked as a security precaution. My posts yesterday received around 3,000 views and no comments. I checked before posting yesterday and there were no similar companies, however, mysteriously today there are several "secure" versions of the same startup I mentioned in the prospectus. (For example https://ontimecall.com/ but there are lots of others, many with long SEO stories that didn't exist yesterday.)
Re:MS Paint Remote Code Execution Vulnerability
by sreekanth850 on Friday November 06, 2026 @12:06AM
(#50388443)
I was saying this is just one case where we can say the reason about copilot, there are dozens of reported vulnerabilities, bugs in kernel, rust. and many more elite products which were authored by so called elite developers.
Re:MS Paint Remote Code Execution Vulnerability
by bigyabai on Friday November 06, 2026 @03:22AM
(#50389599)
You willingly let "perfect" be the enemy of "good" in this case. It's absolutely possible to build software runtimes that obviate this type of nonsense. It's not grandstanding by elite developers, most of these choices are common-sense mitigations.
Re:MS Paint Remote Code Execution Vulnerability
by sreekanth850 on Friday November 06, 2026 @03:36AM
(#50389691)
--Another vulnerability in ssh accounts that should never take a password at all (root, your key-only deploy user, ldap users, the default user on alpine's aws and azure images) take any password longer than 256 characters.
I guess these also belongs to your common sense mitigation category but this has been there since 2016.
-- struct's lifetime requirements can be bypassed via covariant field assignment,
11 year old rust compiler bug. how about this?
Re:MS Paint Remote Code Execution Vulnerability
by pmkary on Friday November 06, 2026 @12:49AM
(#50388670)
Why on Earth do you have to give Paint, internet? How is that a technical debt? Making all nice little fully offline apps Internet Nightmare Slop is wag beyond debt.
Re:MS Paint Remote Code Execution Vulnerability
by infinite_spin on Friday November 06, 2026 @01:11AM
(#50388783)
It might not be paint with internet, it might be something like a packet over your network asking a computer to open an input/file, and the computer responds by opening that malicious input with paint
Re:MS Paint Remote Code Execution Vulnerability
by MarchApril on Friday November 06, 2026 @03:21AM
(#50389589)
Firearms are now exposing the inherent vulnerability of human flesh against small projectiles flying faster than the speed of sound. Before that we were just fist fighting eachother and we were trained for that. But no mo! Get your dragon's breath today at $199.99!
Re:MS Paint Remote Code Execution Vulnerability
by embedding-shape on Friday November 06, 2026 @08:22AM
(#50391996)
> Every program which has telemetry can
I'd go out on a limb here perhaps, but I'd claim that if your telemetry means that the one SENDING the data gets a RCE by default by it, you're doing telemetry very wrong. Maybe look into different libraries/services than the ones you use today, please.
Re:MS Paint Remote Code Execution Vulnerability
by joshspankit on Friday November 06, 2026 @09:42AM
(#50392894)
While I understand your phrasing getting downvoted, I agree with what I assume you mean:
1. Telemetry as implemented is usually sloppy. Even though intuitively one could think that telemetry means “data gets collected locally and fired off to a remote server”, we have seen time and time again that they also build a return path to make the telemetry gathering more powerful. That return path can be a vector.
2. Web browsers have a _huge_ surface and they connect to remote servers constantly. The industry does very well at being proactive and at addressing CVEs but the whole premise makes that very difficult and so we cannot absolutely claim that browsers don’t have RCE(s).
Re:MS Paint Remote Code Execution Vulnerability
by embedding-shape on Saturday November 07, 2026 @06:20AM
(#50403553)
I'm sorry, but I still find it hard to believe you work with other professionals that when they implement telemetry in client applications, that usually ends up exposing a RCE on the client because of the telemetry implementation.
Re:MS Paint Remote Code Execution Vulnerability
by monster_truck on Friday November 06, 2026 @01:45AM
(#50389002)
If I had to guess, without diffing old/new, it's probably related to the generative erase/ai shit.
To stack assumptions, I'd reach for something like using the recent certificate circus to present as there being an updated version of whatever model it uses on the PCs that can run it locally to give it a fucked up model that does the out of bounds shit as part of whatever verification/checks it does after its downloaded/installed.
Re:MS Paint Remote Code Execution Vulnerability
by _notreallyme_ on Friday November 06, 2026 @07:06AM
(#50391396)
Either the description or the impact is wrong. You can't trigger MS Paint in a '0-click' attack, and OOB read are not sufficient to directly obtain code execution. So I'll let you guess which one is wrong.
It's quite common with vulnerabilities found by IA, there might be less hallucination, but the impact/score is often completely wrong.
Re:MS Paint Remote Code Execution Vulnerability
by sharpshadow on Friday November 06, 2026 @10:24AM
(#50393454)
Paint’s image decoding engine is a shared system component and during thumbnail and visual preview generation it gets called automatically without opening the GUI. Ergo it’s enough for a malformed image file to exist on your device to get pwnd.
Re:MS Paint Remote Code Execution Vulnerability
by jasomill on Friday November 06, 2026 @03:43PM
(#50398241)
Do you have details on this? Given that this is classified as a network vulnerability of the Paint application itself rather than any shared system components, I assumed it had to do with the recently-introduced Copilot features which AFAIK are the only part of the application that directly interact with the network.
The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet.
The way I read it is MSPaint is now running as a service and listens to a port (while running? all the time?). Wh?.. Ho?... I can't even...
Re:MS Paint Remote Code Execution Vulnerability
by pmkary on Friday November 06, 2026 @12:45AM
(#50388653)
I love Microsoft! Who else might look at a fully offline drawing app and think: "Man this needs the most severe level of networking access capable of remote code execution", and that surely is to put their useless Copilot to absolutely nowhere. Next headline will be "All user credentials stolen from Notepad"
https://msrc.microsoft.com/update-guide/vulnerability/CVE-20...
> User Interaction: None
> Out-of-bounds read in Windows Paint allows an unauthorized attacker to execute code over a network.
Except for the infamous Dropbox comment.
But remote? How
Or are they chaining a browser auto opening a download in paint, (but browsers shouldn't do that)...
Make a new product and bundle that as an option if you want to drastically change the functionality.
> Notepad in Windows includes AI features powered by Copilot that help refine and shorten text with the assistance of GPT. By default, these AI features are enabled on managed devices
https://learn.microsoft.com/en-us/windows/client-management/...
I mean… what else were the people working on Notepad and Paint to do!?
The order came down to integrate AI, and they wanted to be promoted.
Every single day I’m happier and happier than I use Linux now.
Still, the question remains... How?
> After applying the update, verify that the target Windows systems are running a version that includes the CVE fix before disabling legacy file‑open processing in Paint.
Which is complete nonsense. "Legacy file-open processing" isn't a real configurable option in Paint and this seems to suggest that enabling it is some sort of mitigation. The resolution is simply to update Paint.
Or maybe after the .bmp file is executed, it can install something that opens an outbound TCP connection to its C2, and thus can receive commands. Would not need admin privileges because it doesn't open a port, just 'outbound' connections, like a long-poll.
> The vulnerable system can be exploited without any interaction from any user.
since it exposes no port, I’d assume it isn’t trivial to exploit, paint will chose its target (a microsoft domain or IP), the exploit must involve some error in destination selection, or simply allowing a mitm to impersonate microsoft.
this is inline with Attack Complexity High, attacker needs to be either in the network path (mitm) or control the erroneous destination of the connection (say mircosoft.com), possibly blocking (dosing) the higher priority genuine destination
Should be easy to verify for someone with a windows machine if it does.
So I guess either some random OS component is listening to the network and just-as-inexplicably asking Paint to do something for it. Or one of Paint's outbound connections is vulnerable if hijacked by a mitm. Network interception's one of the examples used for the "High" Attack Complexity rating that MS gave this CVE. Maybe powered by eMudhra for any systems that haven't revoked those certs? That'd be topical.
>Unproven
>Remediation Level
>Official Fix
>Report Confidence
>Confirmed
I really like these secondary scoring factors, not just scoring the vuln itself, but how it's being attacked.
Cross hatch, Scottish tartan?
> An unauthenticated attacker could exploit this vulnerability by sending a specially crafted packet to an affected service over the network. Successful exploitation could allow the attacker to execute code on the target system. No authentication or user interaction is required.
[1] https://msrc.microsoft.com/update-guide/vulnerability/CVE-20...
You haven't declared any privileged knowledge of this attack or MS Paint and have, on vibes, doubled down on what you assume must be going on despite other evidence.
It's a bad look.
You don't have to comment on other people's comments you know.
A significant chunk of the world's problems today are caused by or exacerbated by people who confidently assert things they believe regardless of what evidence or experts say, and who dismiss expertise. Those people are emboldened by others allowing them to spew nonsense unchecked, and I have no interest in seeing HN degraded similarly.
You're moving goalposts. A commenter asked what Networking MS Paint had in the context of this vulnerability. You made an assertion not supported by the documentation we had, and now you're trying to claim that there could be other vulnerabilities rather than admitting that you made a mistake without doing any research.
Normally have been 86-ing a number of annoying things such as OneDrive, but leaving Paint in place figuring it's got to still be harmless.
Creeping increases in attack vector when just the opposite is needed more than ever.
I understood that reference.
Like when a previously sturdy old sailing ship starts taking on water, for instance in the 18th century and beyond.
Numerical equivalent to "deep-six."
Turns out paint was the thing almost every customer had installed/had access to, so he worked to the lowest common denominator and got really good at using it. I guess now he'll need to find a new tool to astonish devs with.
And at the end of the day $2 and $2000 screwdrivers are both still screwdrivers.
Then they added automatic HTML parsing of incoming emails, and the attackers cheered.
You can go back to mutt's parsing, and CVE-1999-0940 for an old example. But I'm sure that's only one of many.
once Microsoft has reinvented themselves as…security-first?
And there is the SFI program.
However this is a Windows application, and in spite some Rust advances in WinDev, it is pretty much C and C++ turf, with Rust getting the same warm reception as .NET used to enjoy.
Guess which language is Paint written on?
Nontheless, they are doubling down on sandboxing Windows, macOS, iOS and Android style, for quite some time, exactly to become security first as you are asking for.
Now that I'm on Linux, I use jspaint.app.
I would use kolourpaint but for whatever reason overlaid GUI elements like the selection box and brush cursors leave trails on the canvas.
Fun anecdote, paint.exe crashed the other day just as I was finishing up my drawing of the tower of Babel.
https://hn.algolia.com/?q=mspaint+ide
[^1]: https://lawsofsoftwareengineering.com/laws/zawinskis-law/
[^2]: https://www.jwz.org/hacks/
Anyway, I continued using layers and transparency/opacity. Pixel art was hard enough already for me, so I didn’t feel that it made sense to artificially make it even more difficult for myself at the time. I had enough other aspects of pixel art to work out already in order to try to get better at it.
There's this https://www.windowsphoneinfo.com/threads/why-does-resizing-m... (made confusing by the next person talking about Paint 3D, a different application) and this https://learn.microsoft.com/en-us/answers/questions/3991946/... (made confusing by the person being an artist and talking in peanut butter metaphors).
But I've only used the program for less than 5 minutes, so maybe it's configured differently?
I don't know why you are so concerned, but it's incredibly easy to test these questions if you really want to know.
The point of paint is a tiny pixel editor. If you want layers there are better programs.
>june 2026
Pretty sure it would be May? But in either case they had 91 releases that month?
They're not a positional notation. It's version 11.2605.91 recently. It was 11.2605.81 earlier this year. There was an 11.2605.71 and an 11.2605.61 before that. Last year, there was a 11.2504.451 . The year before there was a 11.2402.32 .
Microsoft's versioning systems are not 4 columns where a tick around of one increments the one before it. The easiest way to think of them is madness made for marketing purposes. (Windows NT starting at 3.1, for example.) There is some logic to it, but nowadays it's often four entirely different things jammed together, ticking around independently. Like the version of Windows, the year and month of the release, and perhaps a daily build number or some such.
Windows NT itself has a monotonically increasing build number as part of its versioning that started some time in 1992 and is currently just over 26 thousand.
[0] https://x.com/orange_8361/status/2115654643141489057?a=qallN...
UI:N it is with no interaction ?
is it a cve mistake ?
> An unauthenticated attacker could exploit this vulnerability by sending a specially crafted packet to an affected service over the network. Successful exploitation could allow the attacker to execute code on the target system. No authentication or user interaction is required.
Until somebody connects the dots on how the heck MS Paint is accessible over the network, I'm gonna maintain some pretty intense skepticism here.
If I still mamaged any windows host, i would be deploying a remove-package script asap to the entire fleet.
When did y'all stop using some basic sense before writing? -_-
Yeah samesame:
-Compares a kernel with paint
-Uses a program with telemetry/spyware instead of installing on of the 1000s alternatives
Oh no dont get me wrong, it's not random spyware, it's deliberately made spyware by Microsoft targeted at Windows Users.
https://interestingengineering.com/culture/rip-microsoft-pai...
Good for you.
Now only <all Windows users>-1 are affected.
But From [0]: > A total of 59 of the October CVEs fit my definition of wormable. Specifically, 57 contain both “An unauthenticated attacker could exploit this vulnerability by sending a specially crafted packet to an affected service over the network” and “No authentication or user interaction is required.”
Makes you wonder if MS is just copy-pasting boilerplate on CVEs and disclosed incorrectly the scope of the one in Paint because they had 56 other bugs to disclose.
So I'm not discounting reporting human error here, yet.
[0] https://www.zerodayinitiative.com/blog/2026/10/13/the-octobe...
IFF there is a NSA backdoor it likely would be:
- not in paint, but something you can't disable/remove in hardened special purpose windows setups
- not be easily usable by 3rd parties, like some auth accidentally accepting some quite specific other password (e.g. due to some bug reading the expected hash from the wrong place) or similar
lets not forget as much as the NSA might want to spy on you they also want to keep China/Russia out of spying on US companies. A traditional RCE in paint is very counter productive for that.
One one hand they can actively try to work with companies to get secret back doors put in, sure. But I imagine that's not usually very successful. Lavabit chose to go out of business instead of doing so... I wonder who else is out there that we don't know about.
But we also have evidence that they actively look for, buy, and hoard, unknown (to the vendor) exploits for their own possible later use in case they need it for something.
I'm sure you can imagine that it's much more advantageous to keep collecting all kinds of different ways to get into a system in case one method is not applicable for any number of reasons.
not sure if the last time was also a RCE specifically, but this by far isn't the first "this shouldn't even be remotely possible" CVE in MS Paint
The Microsoft link doesn't mention this at all, so my guess it's "remote" in the sense that a zip file exploit is "remote"
This is some Eric-Cantona-level gnomic mysticism. I approve.
https://msrc.microsoft.com/update-guide/vulnerability/CVE-20...
> How could an attacker exploit this vulnerability?
> An unauthenticated attacker could exploit this vulnerability by sending a specially crafted packet to an affected service over the network. Successful exploitation could allow the attacker to execute code on the target system. No authentication or user interaction is required..
unfortunately it made some mistakes and didn't make everything secure.
im sure windows security will get better as models get better...
maybe in six months when we have AGI... . . .
Could also be some kind of recall feature.
I just... It's just ridiculous at this point.
However, the scare mongering caused my posts to be soft locked as a security precaution. My posts yesterday received around 3,000 views and no comments. I checked before posting yesterday and there were no similar companies, however, mysteriously today there are several "secure" versions of the same startup I mentioned in the prospectus. (For example https://ontimecall.com/ but there are lots of others, many with long SEO stories that didn't exist yesterday.)
[1] https://taonexus.com/worthless.txt
[2] creative process: https://imgur.com/a/PO7pvCQ
My take is that the addition of CoPilot to MS Paint is probably how this CVE got introduced.
> LLMs are now unfolding technical debt, poorly written code, and security vulnerabilities accumulated in software that they have created themselves.
We seriously need more information.
I'd go out on a limb here perhaps, but I'd claim that if your telemetry means that the one SENDING the data gets a RCE by default by it, you're doing telemetry very wrong. Maybe look into different libraries/services than the ones you use today, please.
1. Telemetry as implemented is usually sloppy. Even though intuitively one could think that telemetry means “data gets collected locally and fired off to a remote server”, we have seen time and time again that they also build a return path to make the telemetry gathering more powerful. That return path can be a vector.
2. Web browsers have a _huge_ surface and they connect to remote servers constantly. The industry does very well at being proactive and at addressing CVEs but the whole premise makes that very difficult and so we cannot absolutely claim that browsers don’t have RCE(s).
I'm claiming if "everything else" does indeed lead to a RCE, you're again doing something very wrong here. It's not rocket science exactly.
To stack assumptions, I'd reach for something like using the recent certificate circus to present as there being an updated version of whatever model it uses on the PCs that can run it locally to give it a fucked up model that does the out of bounds shit as part of whatever verification/checks it does after its downloaded/installed.
It's quite common with vulnerabilities found by IA, there might be less hallucination, but the impact/score is often completely wrong.
"No User Interaction"
Does that mean that paint doesnt have to be running?
Application being installed on a PC allows a specially crafted packet to arbitrarily execute code?
0. My gut says this is somehow related to indexing/thumbnail rendering. But maybe I'm off base.
1. The 'no user interaction' could be related to (ironically) some background pre-indexing process that windows is doing on files inserted to folders.
1.1. LOL maybe their bullshit 'Windows Copilot' which is why the description is so vague, don't want to torpedo things worse than they already are.
2. It could also be, still in the category of 'well, ok they click on a share folder and the preview runs' or a weird edge thing.
2.1. But they aren't being that clear yet, probably because it's bad.
States:
Attack Vector: Network
The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet.
The way I read it is MSPaint is now running as a service and listens to a port (while running? all the time?). Wh?.. Ho?... I can't even...
This is absurd.
Each time I learn something new about Microslop, I'm just glad I'm not a tenant.