Google releases second Chrome update in a week fixing 83 vulnerabilities including 5 critical use-after-free flaws
On November 11, 2026, Google released another security update for the Chrome Stable channel across Windows, Mac, and Linux platforms, advancing versions to 157.0.8103.78/.79. This update addresses 83 security issues, with five critical severity vulnerabilities classified as use-after-free (UAF) flaws. UAF vulnerabilities occur when software accesses memory that has already been freed, potentially allowing attackers to execute arbitrary code or cause crashes depending on exploitability and mitigations. Users are advised to update immediately by allowing automatic updates or manually via Chrome's About menu to mitigate risks associated with these critical flaws. This rapid follow-up patch highlights the ongoing need for vigilance and prompt update adoption in maintaining browser security.
Entenda a falha
A vulnerabilidade
Google's Chrome Stable update of November 11, 2026 fixes 83 security issues, five of them rated Critical and all five use-after-free (UAF) flaws. The fixed versions are 157.0.8103.78/.79 on Windows and Mac and 157.0.8103.78 on Linux, and the rollout takes days to weeks. The articles give no CVE IDs, components or attack requirements for the individual flaws. In general, a UAF can cause crashes or data corruption, leak information, or in some cases run attacker-controlled code, depending on the component and the protections in place.
Como funciona
The articles do not describe the specific code paths of these five bugs. In a typical UAF, the program releases an object's memory for reuse, but a reference to the old location, a dangling pointer, remains. Later the program uses that reference, although the original object is gone and something else may now occupy that memory. If an attacker can influence what replaces the freed object, the program may treat that data as legitimate data or instructions.
Por que é vulnerável
The articles name the class of bug but not the root cause of each flaw. They say UAF comes from a mistake in managing how long an object stays available: one part of the program frees it while another still expects to use it. Typical triggers are confused ownership, faulty error handling, or timing issues between tasks running at the same time. The articles do not describe what each fix changes.
Como foi descoberta
The articles do not say who found the five Critical flaws or how. They only report that Google published the update on November 11, 2026, two days after the previous Chrome update, which is why the story calls it the second update in a week. They mention no exploitation in the wild.
Explicação gerada por IA a partir da matéria e dos artigos, em 13/11/2026 10:18.
Linha do tempo
-
Google releases second Chrome update in a week fixing 83 vulnerabilities including 5 critical use-after-free flaws
ler a análise desta fonte ocultar
On November 11, 2026, Google released another security update for the Chrome Stable channel across Windows, Mac, and Linux platforms, advancing versions to 157.0.8103.78/.79. This update addresses 83 security issues, with five critical severity vulnerabilities classified as use-after-free (UAF) flaws. UAF vulnerabilities occur when software accesses memory that has already been freed, potentially allowing attackers to execute arbitrary code or cause crashes depending on exploitability and mitigations. Users are advised to update immediately by allowing automatic updates or manually via Chrome's About menu to mitigate risks associated with these critical flaws. This rapid follow-up patch highlights the ongoing need for vigilance and prompt update adoption in maintaining browser security.