It is a libwebp vuln right? So anyone that does not link to libwebp is or may be ok.
Aha! Finally the day has come when KDE's Dolphin emerges as the most secure file manager, in a "this sign can't stop me because I can't read" fashion.
All the proprietary software with their own bundled versions of electron or vendored libraries, etc. on the other hand...
That and every snap/flatpack/etc. package, every container image you are using and possibly pip packages that can come with and compile all kinds of dependencies and haven't been maintained for ten years...
The security benefit a well maintained Linux distro provides has been eroding for years now.
I think there are two problems:
1. people running single/small numbers of servers copying practices that are used by people running fleets of containers who can have someone promptly updating everything has needed. 2. As always, convenience. The easiest and best supported way to pip install things is without --system-site-packages.
I have always felt we were going the wrong way with this. I thought I was the only one!
Firefox very quickly implemented WebP when YouTube (a Google property) added support for animated WebP based hover thumbnails.
Firefox and Safari only caved years later once Chrome-only WebP-only websites were too common to ignore.
The bug is in the codec library, and WebP has implementation monoculture, so everyone uses the same library, and everyone needs to patch.
3. Google tried to make WebP a thing 10 years ago, but it didn't get much traction, since it was Chrome-only for a long time. It never got properly standardized (it is open source tho). It compresses low-quality images better than JPEG, but tends to blur and smear colors in higher-quality images.
Ironically WebP became widely supported at the same time when it became technically obsoleted by AVIF and JPEG XL.