Download 87.0.4280.141 from the Chrome Stable for macOS
Download Google Chrome 87.0.4280.141 with the branch, platform, release date, and file size shown clearly on the same page.
What users usually want to know first
Release overview
Google Chrome 87.0.4280.141 is available here as part of the macOS Stable archive. Use this release page when you want the exact version, the current package details, and quick access to the correct installer.
适用于Windows，Mac和Linux的chrome稳定版已更新为87.0.4280.141，此更新包括16个安全修复程序。
[$20000][1148749] 高危 CVE-2021-21106: 自动填充Use after free(UAF)漏洞.
[$20000][1153595] 高危 CVE-2021-21107: 拖放Use after free(UAF)漏洞.
[$20000][1155426] 高危 CVE-2021-21108: 媒体Use after free(UAF)漏洞.
[$15000][1152334] 高危 CVE-2021-21109: 付款方式Use after free(UAF)漏洞.
[$15000][1152451] 高危 CVE-2021-21110: 安全浏览Use after free(UAF)漏洞.
[$7500][1149125] 高危 CVE-2021-21111: WebUI中的策略执行不足.
[$7500][1151298] 高危 CVE-2021-21112: Blink内核Use after free(UAF)漏洞.
[$6000][1155178] 高危 CVE-2021-21113: Skia基于堆缓冲区溢出漏洞.
[$N/A][1148309] 高危 CVE-2020-16043: 网络中的数据验证不足.
[$N/A][1150065] 高危 CVE-2021-21114: 音频Use after free(UAF)漏洞.
[$TBD][1157790] 高危 CVE-2020-15995: 在V8中越界写操作漏洞.
[$TBD][1157814] 高危 CVE-2021-21115: 安全浏览Use after free(UAF)漏洞.
[$N/A][1151069] 中危 CVE-2021-21116: 音频中的堆缓冲区溢出漏洞.
Installation notes
After downloading the package, confirm that the branch and platform match your device before launching the installer or extracting the archive. If you only need a standard everyday browser, Stable is usually the safest choice. If you are testing new behavior, Beta, Dev, and Canary are better fits.
Related release pages
For newer or older builds in the same branch, open the category archive linked above. For different platforms, use the related desktop archives in the sidebar.
Frequently asked questions
These FAQ blocks help the page read like a complete release article instead of a download stub, which is better for trust and better for SEO.
Should I use this release or stay on Stable?
If you just want the safest everyday browsing experience, Stable is usually the right default. Preview branches are better for testing, compatibility checks, and early feature access.
Why show exact version numbers so prominently?
Because exact-version queries are common in English search behavior, especially for QA teams, enterprise users, and people trying to reproduce a bug or environment.
Why keep a full article around the download buttons?
A stronger page body gives users context and gives Google clearer signals about what the release page actually covers.
Where should older releases live?
Older versions belong in the category archive page, with this article template handling exact-version landing pages one release at a time.