News for hackers. Stuff that matters.
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 Kapura on Thursday November 05, 2026 @06:43PM (#50386201)
This was my observation too; I assume 11.0.0.0 is windows 11? because my windows 10 mspaint doesn't even match that numbering format.
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 tjohns on Thursday November 05, 2026 @07:03PM (#50386362)
[delayed]
Re:MS Paint Remote Code Execution Vulnerability by StilesCrisis on Thursday November 05, 2026 @07:14PM (#50386456)
The Windows 11 version is a complete rewrite.
Re:MS Paint Remote Code Execution Vulnerability by CursedSilicon on Thursday November 05, 2026 @07:19PM (#50386500)
So was the Windows 7 version
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 Kwpolska on Friday November 06, 2026 @03:15AM (#50389557)
They also added brushes and shapes, they might have rewritten it at that point.
Re:MS Paint Remote Code Execution Vulnerability by jval43 on Thursday November 05, 2026 @07:14PM (#50386459)
They added AI.
Re:MS Paint Remote Code Execution Vulnerability by Legend2440 on Thursday November 05, 2026 @07:33PM (#50386616)
They've added a lot of features and it's almost like Photoshop Elements now. It has layers, general photo editing tools, an AI generator, etc.
Re:MS Paint Remote Code Execution Vulnerability by anal_reactor on Thursday November 05, 2026 @08:39PM (#50387074)
I remember that when Paint started being funky I found a Windows XP exe and used that. I want Paint to be the graphical equivalent of hexedit.

Now that I'm on Linux, I use jspaint.app.

Re:MS Paint Remote Code Execution Vulnerability by WarOnPrivacy on Thursday November 05, 2026 @11:57PM (#50388402)
Windows 11 26H2 w/ MSPaint is 10.26100.1. It's just right.
Re:MS Paint Remote Code Execution Vulnerability by boomlinde on Friday November 06, 2026 @03:21AM (#50389592)
I still use the Paint from Windows XP, running in Wine.

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.

Re:MS Paint Remote Code Execution Vulnerability by bombcar on Thursday November 05, 2026 @08:39PM (#50387077)
Just like any text editor is doomed to become either Emacs or Word, so any image editor is doomed to become Photoshop.
Re:MS Paint Remote Code Execution Vulnerability by wilkystyle on Thursday November 05, 2026 @09:27PM (#50387385)
Too true. I gave up trying to fight it years ago and now write all my documents in Emacs and edit my code with Microsoft Word.
Re:MS Paint Remote Code Execution Vulnerability by jodrellblank on Thursday November 05, 2026 @11:24PM (#50388172)
Did you miss the chance to edit your code with MS Paint as your IDE?

https://hn.algolia.com/?q=mspaint+ide

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."

[^1]: https://lawsofsoftwareengineering.com/laws/zawinskis-law/

[^2]: https://www.jwz.org/hacks/

Re:MS Paint Remote Code Execution Vulnerability by sam345 on Friday November 06, 2026 @12:30AM (#50388571)
Except Vim of course.
Re:MS Paint Remote Code Execution Vulnerability by eru on Friday November 06, 2026 @07:11AM (#50391436)
Well, there's vile for you.
Re:MS Paint Remote Code Execution Vulnerability by pasteleft on Thursday November 05, 2026 @09:34PM (#50387441)
Honestly I like layers in Paint. Even pixel art programs have layers.
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 card_zero on Friday November 06, 2026 @07:29AM (#50391567)
But is Windows 11 paint capable of pixel art? I'm reading that it antialiases everything.
Re:MS Paint Remote Code Execution Vulnerability by Measter on Friday November 06, 2026 @08:08AM (#50391885)
You can draw single pixels. I'm not sure where whoever told you that got it from.
Re:MS Paint Remote Code Execution Vulnerability by card_zero on Friday November 06, 2026 @08:13AM (#50391922)
But can you resize without antialiasing, and does pasting trigger antialiasing?

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).

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 IAmBroom on Friday November 06, 2026 @05:21PM (#50399292)
Yes, resizing within Paint preserves pixel-level color. I just resized a single pixel dot to about 14x25 without aliasing.

I don't know why you are so concerned, but it's incredibly easy to test these questions if you really want to know.

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 rkachowski on Friday November 06, 2026 @07:52AM (#50391741)
XP era mspaint with layers is really all I want. Rudimentary image editing and drawing but with layers.
Re:MS Paint Remote Code Execution Vulnerability by IAmBroom on Friday November 06, 2026 @05:21PM (#50399295)
Add threshold select (magic wand), and I'll agree 100%.
Re:MS Paint Remote Code Execution Vulnerability by breakwaterlabs on Friday November 06, 2026 @12:28PM (#50395419)
They should have just hired the paint.net guy and rolled it in.

The point of paint is a tiny pixel editor. If you want layers there are better programs.

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 @08:16PM (#50386951)
It's the last two digits of the year plus the month number. That was June 2026. It was 2504 in May 2025, and 2402 in March 2024.
Re:MS Paint Remote Code Execution Vulnerability by what on Thursday November 05, 2026 @09:18PM (#50387319)
>2605

>june 2026

Pretty sure it would be May? But in either case they had 91 releases that month?

Re:MS Paint Remote Code Execution Vulnerability by gnabgib on Thursday November 05, 2026 @09:21PM (#50387337)
Call a paleontologist, it kooks like we've found a Java developer
Re:MS Paint Remote Code Execution Vulnerability by Rexxar on Thursday November 05, 2026 @09:26PM (#50387373)
Maybe someone insisted to start counting month at zero.
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 hulitu on Friday November 06, 2026 @01:25AM (#50388871)
They didn't get the right roundness from the first time. /s
Re:MS Paint Remote Code Execution Vulnerability by HoldOnAMinute on Thursday November 05, 2026 @10:44PM (#50387897)
Ads, subscriptions, AI
Re:MS Paint Remote Code Execution Vulnerability by sznio on Friday November 06, 2026 @01:01AM (#50388733)
it seems to be the same version/build as the whole system
Re:MS Paint Remote Code Execution Vulnerability by hulitu on Friday November 06, 2026 @01:23AM (#50388857)
Did you noticed the round buttons lately ?
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 novia on Thursday November 05, 2026 @08:20PM (#50386971)
My version shows "22H2"
Re:MS Paint Remote Code Execution Vulnerability by lossyalgo on Thursday November 05, 2026 @09:25PM (#50387368)
[delayed]
Re:MS Paint Remote Code Execution Vulnerability by cowlevel on Thursday November 05, 2026 @10:42PM (#50387887)
Or if you're using Linux. Or OSX. seL4 users are safe though, mostly because their computers don't do anything useful.
Re:MS Paint Remote Code Execution Vulnerability by durmusk on Friday November 06, 2026 @12:12AM (#50388473)
That is Windows version. But you probably use the regular Win32 Paint, so should be okay.