Apple aids app development with new intelligence frameworks and advanced tools


The Extended Stable channel has been updated to 148.0.7778.254 for Windows and Mac which will roll out over the coming days/weeks.
The Stable channel has been updated to 149.0.7827.102/.103 for Windows andΒ Mac and 149.0.7827.102 for Linux, which will roll out over the coming days/weeks. A full list of changes in this build is available in the Log
Security Fixes and Rewards
Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but havenβt yet fixed.
This update includes 74 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information
[N/A][516501794] Critical CVE-2026-11628: Use after free in Ozone. Reported by Google on 2026-05-25
[N/A][516674532] Critical CVE-2026-11629: Use after free in Ozone. Reported by Google on 2026-05-26
[N/A][516677924] Critical CVE-2026-11630: Use after free in File Input. Reported by Google on 2026-05-26
[N/A][516691130] Critical CVE-2026-11631: Use after free in Aura. Reported by Google on 2026-05-26
[N/A][516707881] Critical CVE-2026-11632: Use after free in TabStrip. Reported by Google on 2026-05-26
[N/A][516963272] Critical CVE-2026-11633: Use after free in Bluetooth. Reported by Google on 2026-05-27
[N/A][516975148] Critical CVE-2026-11634: Use after free in Gamepad. Reported by Google on 2026-05-27
[N/A][516987814] Critical CVE-2026-11635: Use after free in Bluetooth. Reported by Google on 2026-05-27
[N/A][517023053] Critical CVE-2026-11636: Use after free in Autofill. Reported by Google on 2026-05-27
[N/A][517040438] Critical CVE-2026-11637: Use after free in Views. Reported by Google on 2026-05-27
[N/A][517047197] Critical CVE-2026-11638: Use after free in Printing. Reported by Google on 2026-05-27
[N/A][517227707] Critical CVE-2026-11639: Use after free in Compositing. Reported by Google on 2026-05-27
[N/A][517339758] Critical CVE-2026-11640: Integer overflow in libyuv. Reported by Google on 2026-05-28
[N/A][517418936] Critical CVE-2026-11641: Use after free in Bluetooth. Reported by Google on 2026-05-28
[N/A][517678820] Critical CVE-2026-11642: Use after free in Web Apps. Reported by Google on 2026-05-29
[N/A][518006379] Critical CVE-2026-11643: Use after free in Proxy. Reported by Google on 2026-05-29
[N/A][518043597] Critical CVE-2026-11644: Use after free in Views. Reported by Google on 2026-05-30
[$55000][506689381] High CVE-2026-11645: Out of bounds memory access in V8. Reported by 303f06e3 on 2026-04-27
[$500][517168239] High CVE-2026-11646: Use after free in ViewTransitions. Reported by Quac Tran on 2026-05-27
[N/A][502156940] High CVE-2026-11647: Use after free in Printing. Reported by Google on 2026-04-13
[N/A][506684534] High CVE-2026-11648: Use after free in FullScreen. Reported by Mihnea Nicolau on 2026-04-27
[N/A][511270083] High CVE-2026-11649: Use after free in V8. Reported by Google on 2026-05-08
[N/A][511279942] High CVE-2026-11650: Use after free in V8. Reported by Google on 2026-05-08
[N/A][511736002] High CVE-2026-11651: Use after free in Network. Reported by Google on 2026-05-10
[N/A][513156160] High CVE-2026-11652: Use after free in Extensions. Reported by Google on 2026-05-14
[N/A][513321171] High CVE-2026-11653: Insufficient validation of untrusted input in Extensions. Reported by Google on 2026-05-14
[N/A][513362710] High CVE-2026-11654: Use after free in CameraCapture. Reported by Google on 2026-05-15
[N/A][513396305] High CVE-2026-11655: Integer overflow in Media. Reported by Google on 2026-05-15
[N/A][513424000] High CVE-2026-11656: Use after free in ServiceWorker. Reported by Google on 2026-05-15
[N/A][513465272] High CVE-2026-11657: Use after free in Payments. Reported by Google on 2026-05-15
[N/A][513564337] High CVE-2026-11658: Insufficient validation of untrusted input in Extensions. Reported by Google on 2026-05-15
[N/A][513702971] High CVE-2026-11659: Insufficient validation of untrusted input in UI. Reported by Google on 2026-05-16
[N/A][513731890] High CVE-2026-11660: Insufficient validation of untrusted input in New Tab Page. Reported by Google on 2026-05-16
[N/A][513748868] High CVE-2026-11661: Use after free in Views. Reported by Google on 2026-05-16
[N/A][513773313] High CVE-2026-11662: Type Confusion in Bindings. Reported by Google on 2026-05-16
[N/A][513820666] High CVE-2026-11663: Use after free in Skia. Reported by Google on 2026-05-16
[N/A][513830374] High CVE-2026-11664: Use after free in Payments. Reported by Google on 2026-05-16
[N/A][513948465] High CVE-2026-11665: Out of bounds read in Dawn. Reported by Google on 2026-05-17
[N/A][514009323] High CVE-2026-11666: Insufficient validation of untrusted input in Input. Reported by Google on 2026-05-17
[N/A][514671098] High CVE-2026-11667: Out of bounds read in WebRTC. Reported by Google on 2026-05-19
[N/A][515419790] High CVE-2026-11668: Uninitialized Use in Codecs. Reported by Google on 2026-05-21
[N/A][515429352] High CVE-2026-11669: Integer overflow in Media. Reported by Google on 2026-05-21
[N/A][515469283] High CVE-2026-11670: Use after free in PDF. Reported by Google on 2026-05-21
[N/A][516608438] High CVE-2026-11671: Use after free in Navigation. Reported by Google on 2026-05-26
[N/A][516794471] High CVE-2026-11672: Out of bounds write in GPU. Reported by Google on 2026-05-26
[N/A][516902973] High CVE-2026-11673: Use after free in InterestGroups. Reported by Google on 2026-05-26
[N/A][516910450] High CVE-2026-11674: Use after free in Guest View. Reported by Google on 2026-05-27
[N/A][516915337] High CVE-2026-11675: Insufficient validation of untrusted input in Skia. Reported by Google on 2026-05-27
[N/A][516949298] High CVE-2026-11676: Insufficient validation of untrusted input in Dawn. Reported by Google on 2026-05-27
[N/A][516979551] High CVE-2026-11677: Race in Network. Reported by Google on 2026-05-27
[N/A][516986556] High CVE-2026-11678: Integer overflow in libyuv. Reported by Google on 2026-05-27
[N/A][516997135] High CVE-2026-11679: Use after free in Codecs. Reported by Google on 2026-05-27
[N/A][517004487] High CVE-2026-11680: Use after free in Media. Reported by Google on 2026-05-27
[N/A][517050585] High CVE-2026-11681: Use after free in Ozone. Reported by Google on 2026-05-27
[N/A][517103584] High CVE-2026-11682: Insufficient validation of untrusted input in Views. Reported by Google on 2026-05-27
[N/A][517129549] High CVE-2026-11683: Use after free in WebCodecs. Reported by Google on 2026-05-27
[N/A][517130229] High CVE-2026-11684: Insufficient policy enforcement in Network. Reported by Google on 2026-05-27
[N/A][517183713] High CVE-2026-11685: Insufficient data validation in MediaCapture. Reported by Google on 2026-05-27
[N/A][517247333] High CVE-2026-11686: Insufficient validation of untrusted input in Dawn. Reported by Google on 2026-05-27
[N/A][517303276] High CVE-2026-11687: Use after free in Dawn. Reported by Google on 2026-05-28
[N/A][517309206] High CVE-2026-11688: Object lifecycle issue in SVG. Reported by Google on 2026-05-28
[N/A][517486004] High CVE-2026-11689: Insufficient validation of untrusted input in Passwords. Reported by Google on 2026-05-28
[N/A][517533654] High CVE-2026-11690: Out of bounds read and write in Media. Reported by Google on 2026-05-28
[N/A][517585486] High CVE-2026-11691: Insufficient validation of untrusted input in New Tab Page. Reported by Google on 2026-05-28
[N/A][517607902] High CVE-2026-11692: Use after free in Read Anything. Reported by Google on 2026-05-28
[N/A][517644287] High CVE-2026-11693: Inappropriate implementation in Plugins. Reported by Google on 2026-05-28
[N/A][517705966] High CVE-2026-11694: Use after free in ServiceWorker. Reported by Google on 2026-05-29
[N/A][517762104] High CVE-2026-11695: Inappropriate implementation in Passwords. Reported by Google on 2026-05-29
[N/A][517993381] High CVE-2026-11696: Uninitialized Use in Video. Reported by Google on 2026-05-29
[N/A][518105731] High CVE-2026-11697: Insufficient validation of untrusted input in UI. Reported by Google on 2026-05-30
[N/A][518235412] High CVE-2026-11698: Use after free in Bluetooth. Reported by Google on 2026-05-30
[N/A][518237527] High CVE-2026-11699: Use after free in Bluetooth. Reported by Google on 2026-05-30
[N/A][511732085] Medium CVE-2026-11700: Use after free in Tracing. Reported by Google on 2026-05-10
[N/A][516413817] Medium CVE-2026-11701: Insufficient validation of untrusted input in Guest View. Reported by Google on 2026-05-25
Google is aware that an exploit for CVE-2026-11645 exists in the wild.
We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel.
Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL.
Interested in switching release channels? Find out how here. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.
Daniel Yip
Google Chrome






Important
This version contains critical security fixes, it is recommended to update to this version immediately.
APP_SECRET env must be changed to prevent forgery of REMEMBERME tokens. To be doable an attacker requires to know the secret password hash of a user, which is not obtainable without another security issue. Administrators will see an warning banner on the homepage, asking to change the APP_SECRET.Generate an new random 32 character string with openssl rand -hex 32 and put the value for APP_SECRET into your .env.local or the environment section of the docker-compose.yaml.
2.0.1
2.0.1
2.0.1
Important
This release includes breaking changes. Review the migration guide before updating.
Full Changelog: v1.20.0...v2.0.0
2.0.0
2.0.0
2.0.0
We're excited to share that we'll be attending the Rock for People 2026Β music festival in Hradec KrΓ‘lovΓ©, Czech Republic. We've been invited by PlayStation CZ to their gaming hangar at the eventΒ with our 4D Motion Simulator, where you'll be able to play our games!
From the 10th to 14th of June, we'll be part of the 31st edition of this iconic festival, taking place at Park 360 in Hradec KrΓ‘lovΓ©. You'll find us in the PlayStation Hangar, located near the main entrance, where visitors will have the opportunity to experience our games on our immersive 4D Motion Simulator and meet some of our colleagues.
Rock for People welcomed more than 50,000 visitors last year, and we're thrilled to be part of this incredible event. While you're enjoying the music and atmosphere, make sure to stop by, say hello to our colleagues, and enjoy a ride on our simulator!
You can find more information about the Rock For People festival here. We would also like to send a huge thank you to PlayStation CZΒ for inviting us to this fantastic event. We can't wait to see you there!
For more news from other events and our games, remember to give our X/Twitter, Instagram, Facebook, Bluesky, and TikTokΒ or subscribe to our newsletter to stay informed! Until next time, keep on truckin'.
A new minor release 0.4.27 of RQuantLib, the first in over a year, arrived on CRAN a couple of minutes ago, has just now been uploaded to Debian, and is being built for r2u as well.
QuantLib is a rather comprehensice free/open-source library for quantitative finance. RQuantLib connects (some parts of) it to the R environment and language, and has been part of CRAN for nearly twenty-three years (!!) as it was one of the first packages I uploaded to CRAN.
This release of RQuantLib
brings an update to the interface for all equity options, vanilla and
exotics as well as implied volatilities. We now support the option
maturity via either an actual maturity date, or the (fractional
business-day years) numeric. This uses a clever little Rcpp trick I should discuss in a
separate blog post. We also re-ran compileAttributes() to
re-create the RcppExports.cpp file now using a slightly
improved way of calling Rf_error for an ongoing Rcpp transition, and did some more
standard maintenance. The details from the NEWS file follow as
usual.
Changes in RQuantLib version 0.4.27 (2026-06-07)
All equity option functions can now take either a (fractional) time span to expiry or a given date, and accept a daycounter setter.
Two very old schedule helpers had a superfluous
try/catchremoved.The continuous integration setup received a minor update.
The
RcppExports.cppfile was updated to aid aRcpptransition.
Courtesy of my CRANberries, there is also a diffstat report for the this release. As always, more detailed information is on the RQuantLib page. Questions, comments etc should go to the rquantlib-devel mailing list. Issue tickets can be filed at the GitHub repo.
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. If you like this or other open-source work I do, you can now sponsor me at GitHub.
I finally carved out some time today to prepare and release debsecan-mcp v0.1.2 to PyPI. During this release, I integrated PyPI's trusted publisher mechanism, which authenticates directly via GitHub Actions and eliminates the need for manual uploads or static API tokens.
There are no feature updates in this release; the changes are strictly focused on PyPI publishing requirements. This was handled entirely within the Antigravity IDE.
The primary change replaces the python-apt dependency with python-debian for version comparison. PyPI rejects packages that reference external Git repositories, and python-apt lacks an official PyPI release. The original python-apt logic remains intact: if the system has python-apt installed, the server defaults to it. Otherwise, it falls back to the comparison logic implemented via the python-debian NativeVersion class.
The next release will introduce a standalone CLI utility called debvulns. It mirrors debsecan functionality but surfaces the cleaner, richer vulnerability data already implemented in debsecan-mcp. The code is written, and I will release it once testing is complete.
I also owe a post explaining my rationale for designing a CLI utility alongside the MCP server, and my broader thoughts on CLI vs. MCP workflows. I aim to publish that next week.
Release created in https://github.com/OpenRCT2/OpenRCT2/actions/runs/27089751091
SHA256 checksums:
08869f7e5f34b44920a4209a0d81b2fb688b8fabb16fd23d7d486536e2f9e482 ./OpenRCT2-v0.5.2-linux-x86_64.AppImage
162c61e65f4327d3d5406dcfebc0b634ba6a0c8b1d8a71fb12f7a14cebd3a158 ./OpenRCT2-v0.5.2-Linux-trixie-x86_64.tar.gz
73f114744a5f44c63225db7a3897158addc83094797e52069d000b007d63a508 ./OpenRCT2-v0.5.2-windows-installer-win32.exe
f433cffae1cee88f71de0bb4a296d3c63b4802f907e08078c019d10a475bf050 ./OpenRCT2-v0.5.2-windows-installer-x64.exe
54715dacc97370a38f83572d609135a9ef395324ae38fd6ae3864aa6de958d0d ./OpenRCT2-v0.5.2-Linux-resolute-x86_64.tar.gz
34477e8339107d94ff441c99d00f6e94a26e481ab97727c4b744ab01b38d842a ./OpenRCT2-v0.5.2-windows-symbols-x64.zip
2d8e436217a2351eeb016715652f205d8c1f21f7467b25e0f9895b8175a1040a ./OpenRCT2-v0.5.2-windows-symbols-win32.zip
17561e865947ac69394fc21a978102b36b6a3681fd2e22bda45162f223a7d5f4 ./OpenRCT2-v0.5.2-windows-symbols-arm64.zip
3c0ab35a415907c883628a7113a20607041c00c2ef60419da0f2ebffcf0e5c8a ./OpenRCT2-v0.5.2-windows-installer-arm64.exe
247230c20657d5ae55494a6a5fb80f3050ef573c6be880a782283cf587813585 ./OpenRCT2-v0.5.2-windows-portable-win32.zip
6bc105b4fa9c751e17ffa13af68a6070f8a0956b713d2602fcbf67d3380c945f ./OpenRCT2-v0.5.2-sha256sums.txt
1e5bea5f11dcd44e803ecf6b51242ac33ae1ce3a5186ed07362c05fba7604892 ./OpenRCT2-v0.5.2-windows-portable-arm64.zip
b80fd9b439fb42d1c4d58245fb9215bbea89813326e3616b72e95181a8d06787 ./OpenRCT2-v0.5.2-macos-universal.zip
e5aea2add0bc140dc1a0b2bde6b02cbf569656ba4e0e4bf1402c99be6540b7d9 ./OpenRCT2-v0.5.2-windows-portable-x64.zip
262f57a8b1859e58b5319e3aee12062d215170868b9ded5d963c67d53dce6b5d ./OpenRCT2-v0.5.2-Linux-noble-x86_64.tar.gz
1cbe1db375094d64af72df042f291bbc92386fb63970c8260bc3cd1547cd842d ./OpenRCT2-v0.5.2-android.apk
8f13a7d3a624f2ff56dd55545c6e38691801cb159065e5c56b12eebc818a5a95 ./OpenRCT2-v0.5.2-Linux-bookworm-x86_64.tar.gz
A while back, I got my first subwoofer (a surprisingly nice addition to the movie experience, just like rear speakers were). But I live in an apartment, and I don't want to annoy my neighbors at night (the speaker cone points literally down into the floor, and I have no idea how much my neighbors get to share in my enjoyment). So, what to do?
It turns out my receiver supports a sort-of documented serial protocol; it doesn't have an actual serial port, but you can telnet into it (only one session at a time!) and get the same two-way stream. (It also has a HTTP version which I find less useful.) So this allows me to impose my own policy, and of course, doing it via an existing Home Assistant adapter or something was no fun and also thoroughly frustrating, so I saw it as an opportunity to keep maintaining my low-key Rust skills. (No, no LLM code generation. If I'm going to spend time on this, at least I can learn something myself. I think I asked one for code critique at some point, but I can't remember.)
The policy is roughly: If I'm watching TV after 22:00, then the subwoofer is either turned off (if possible) or turned down -12 dB (the maximum). But if I'm watching a Blu-ray or another input like that, that's presumably a conscious tradeoff I've made and things are left at normal. Everything gets a bit more complicated by the fact that the receiver tends to lose state when doing certain switches, and when it boots, it takes a minute or two before Telnet responds, and when it shuts down, it goes into this weird limbo state where it doesn't respond to anything but the TCP connection seems still up.
And then I figured out I also wanted to dim the display when watching movies (again, only certain inputs), but not for a couple of seconds after making any adjustments. And after doing that, I figured that my access point LED should also be turned off, which happens to be some SNMP writable stuff against the Cisco wireless controller it hangs on.
So, if you have a Denon or Marantz AVR, a Cisco access point on a controller, and my exact preferences about what to do about the subwoofer, then you are free to download and use my software to impose that policy. It is βis distributed in the hope that it will be usefulβ, as one says. If you have IPv6.
This was my hundred-forty-third month that I did some work for the Debian LTS initiative, started by Raphael Hertzog at Freexian.
During my allocated time I uploaded or worked on:
This was a rather strange month. The details about the embargoed exim4 issue arrived only after I already went to bed and the embargo lift was 18 hours later. Luckily Stretch was not really affected and the uploads for Bullseye and Buster went out on time.
Something similar happened with the embargoed issue of rsync. The info arrived at 8:00 in the morning and the embargo lift was on 2:00 next morning. From an Europeans point of view, the Australians do have strange time zones. But there is more to this than that. Upstream sent more than 50(!) patches for these five CVEs that needed a backport to Bullseye. As things turned out, there is a regression in the upload to Unstable and investigations are ongoing whether this regression is also available in the backported patches for Trixie, Bookworm and Bullseye. So rsync-updates for Buster and Stretch is in the works, but I am afraid they need some more time.
All good things come by threes. Two critical CVEs of hplip appeared and a new upstream version was released by HP. HP is no longer interested in working with distributions and over time more than 80 patches have been accumulated that need a rebase for a new upstream version. For that reason I avoid this package as much as I can, but two critical CVEs did apply some kind of pressure on the maintainer. So I finally managed to do this update and the latest version of hplip is now in Debian. Nevertheless, this feels good :-). Anyway, it is not over yet. HP does not have a public repository nor do they publish patches for these CVEs. So I am still searching for the correct fixes to backport them to Bullseye, Buster and Stretch. The other distributions have the same problem and a silver lining appears on the horizon.
I also prepared an update of gimp for Buster and Stretch, but due to an accident I only managed to release the corresponing ELA in June. The accident was also the reason for only half a week of FD. Thanks to Daniel who took over.
This month I uploaded a new upstream versions:
This work is generously funded by Freexian!
This month I continued to work on unifying packaging on Debian and Ubuntu. This makes it easier to work on those packages independent of the used platform.
This work is generously funded by Fre(i)e Software GmbH!
This month I uploaded a new upstream version or a bugfix version of:
This month I uploaded a new upstream version or a bugfix version of:
This month I uploaded a new upstream version or a bugfix version of:
I also got rid of gypsy, which no longer makes sense to maintain in Debian, as gpsd is way better.
This is the 14th update to ElegantFin.
--resumeCardScale (#248).--menuButtonVisibility.title attribute, resolving several icon alignment issues.--artistTitleVisibility, --artistClearLogoVisibility and --artistPageBackground.gap on phones to create a more predictable and maintainable layout system similar to desktops.You may use the provided CSS file for self-hosting purposes. Alternatively, you may use the following code snippet to get the latest version via a free CDN.
@import url("https://cdn.jsdelivr.net/gh/lscambo13/ElegantFin@main/Theme/ElegantFin-jellyfin-theme-build-latest-minified.css");
For more detailed information, be sure to read the README.md file.