β’ Vivaldi: 7.7.3851.61 π
β’ Chrome: 143.0.7499.40
β’ Chrome ESR: 142.0.7444.226
β’ Firefox: 146.0
β’ Firefox ESR: 140.6.0
β’ Safari: 26.1
β’ Edge: 143.0.3650.66
β’ Opera: 125.0.5729.15
β’ Brave: 1.85.111
β’ Gnome Web: 49.2
β’ WebKitGTK: 2.50.3
If you have a fediverse account, you can quote this note from your own instance. Search https://social.vivaldi.net/users/browserversiontracker/statuses/115695393613130159 on your instance and quote it. (Note that quoting is not supported in Mastodon.)
I see that Brendan Eich from Brave is out lying about
@Vivaldi again. He claims that Brave was pretty much the first out with a fix for CVE-2025-14174 and that Vivaldi still has not released a fix.
AFAIK we were actually first because we released 7.7.3862.88 (Android) based on 142.0.7444.237 from the Extended Support Release branch at 13:00 UTC (and for Desktop [7.7.3851.61] one hour later) on the 10th of December (the day before Brave and even before Chrome), which includes a fix for CVE-2025-14174. However since that CVE was not being publicly discussed yet, it was not initially listed in the changelog.
I have updated the Desktop announcement to mention the CVE now. Here it is:
https://vivaldi.com/blog/desktop/minor-update-five-7-7/
Also FWIW my Masto bot which tracks various desktop browser updates announced us here:
https://social.vivaldi.net/@browserversiontracker/115695393613130159
That bot has a sibling that looks at Vivaldi only releases (all platforms), which caught the Android release:
https://social.vivaldi.net/@vivaldiversiontracker/115695161453809439
And here is when it detected the Brave annoucement, more than a day later:
https://social.vivaldi.net/@browserversiontracker/115702471419843978