{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidotq42oyjus6eflmtdwdjsfbsx4o6xo4ysikc4b7amrn3ifvmrom",
    "uri": "at://did:plc:s3thzwev737hi5yrya3vm4xn/app.bsky.feed.post/3mfkw6aqa4ys2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreidnhbhyqg7lco72p2ma72feccspc274tii5i5vmnkhf5nythw462m"
    },
    "mimeType": "image/png",
    "size": 14109
  },
  "path": "/2026/02/stable-channel-update-for-desktop_23.html",
  "publishedAt": "2026-02-23T21:24:00.000Z",
  "site": "http://chromereleases.googleblog.com",
  "tags": [
    "Log",
    "3",
    "Chrome Security Page",
    "TBD][[ 482862710",
    "TBD][[483751167",
    "TBD][[485287859",
    "[NA",
    "AddressSanitizer",
    "MemorySanitizer",
    "UndefinedBehaviorSanitizer",
    "Control Flow Integrity",
    "libFuzzer",
    "AFL",
    "here",
    "filing a bug",
    "community help forum"
  ],
  "textContent": " The Stable channel has been updated to 145.0.7632.116/117 for Windows/Mac  and 144.0.7559.116 for Linux, which will roll out over the coming days/weeks. A full list of changes in this build is available in the Log\n\n\n\n\nSecurity Fixes and Rewards\n\n _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.\n\n_\n\nThis update includes 3 security fixes. Please see the Chrome Security Page for more information.\n\n**\n**\n\nTBD][[ 482862710] High CVE-2026-3061: Out of bounds read in Media. Reported by Luke Francis on 2026-02-09\n\nTBD][[483751167] High CVE-2026-3062: Out of bounds read and write in Tint. Reported by cinzinga on 2026-02-11\n\nTBD][[485287859] High CVE-2026-3063: Inappropriate implementation\n\nin DevTools. Reported by M. Fauzan Wijaya (Gh05t666nero) on 2026-02-17\n\n**\n**\n\nWe would also like to thank all security researchers that worked with us during\n\nthe development cycle to prevent security bugs from ever reaching the stable channel.\n\nAs usual, our ongoing internal security work was responsible for a wide range of fixes:\n\n  * [NA]Various fixes from internal audits, fuzzing and other initiatives\n\n\n\n\n\n\nMany of our security bugs are detected using AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL.\n\n\n\n\n\n\n\nInterested 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.\n\n\n\n\nKrishna Govind\n\nGoogle Chrome",
  "title": "Stable Channel Update for Desktop",
  "updatedAt": "2026-02-23T21:24:15.414Z"
}