Google Patches Actively Exploited V8 Zero-Day in Chrome (CVE-2026-85046)
Google has distributed an urgent update for Chrome to fix CVE-2026-85046, a zero-day vulnerability in the V8 engine that is under active exploitation. Users must update to Chrome 152.0.7977.82 or later and restart the browser to apply the patch.
The vulnerability is a type confusion flaw in V8, the JavaScript and WebAssembly engine. It resides in the Maglev compiler and affects optimizations related to Array.prototype.sort. Certain inlining and specialization decisions can leave the engine in an inconsistent state, enabling attackers to build reliable exploitation chains that achieve arbitrary memory access within the JavaScript heap.
An attacker can trigger the flaw by serving a malicious HTML page, a technique commonly seen in malvertising, compromised sites, or phishing campaigns. The published CVSS score is 8.8, reflecting the requirement for user interaction.
Google fixed the issue in the stable desktop channel with versions 152.0.7977.82 and 152.0.7977.83 for Windows and macOS, and 152.0.7977.82 for Linux. The update also resolves 11 additional vulnerabilities, bringing the total to 12 fixes.
The researcher Salvatore Gulizia, operating under the handle Serotav, reported the bug on 4 August 2026 and received a $1,000 reward. Google continues its policy of limiting technical details until the majority of users have updated.
Administrators should accelerate patch deployment, verify installed versions, and prioritize high-exposure systems. Users of other Chromium-based browsers, including Microsoft Edge, Brave, Opera, and Vivaldi, must apply updates from their respective vendors once available.
Related articles
Negative Specifications: How Bug History Strengthens AI Agent Code for Ginux Kernel
The article explores how incomplete positive specifications lead to vulnerabilities and compatibility gaps when AI agents develop complex systems like the Ginux kernel. Author sgordey describes discovering memory limit bypasses, domain controller takeover via infinite loops, and ineffective SO_REUSEADDR flags during security audits of the Rust-written Linux-compatible kernel created by Gregory Kurtzer using HDAE methodology. It argues for building negative specifications drawn from historical vulnerabilities such as SACK Panic and SACK Slowness to define what must never happen and how to test it. The piece details practical integration of past bug data into frameworks including BMAD, OpenSpec, Kiro, and Superpowers, recommending dedicated steps like failure-history and challenge-spec tasks before coding begins. Tools rust-in-peace and reproof already apply similar multi-angle searches combining threat modeling, unaided discovery, and CVE history. The author stresses that requirements derived from real failures must enter both specifications and test plans to prevent agents from repeating known mistakes.
Proving Vulnerability Management Works: MTTR Metrics, Maturity Models, and Real-World Testing
This article explains how organizations can measure the effectiveness of their vulnerability management programs using key metrics like MTTR, coverage, and maturity levels. It emphasizes that without proper measurement, even advanced scanners and skilled teams cannot confirm whether the process is functioning or stalling. The piece highlights MTTR as the primary metric for executive discussions because it directly correlates with real-world exploit timelines. Industry benchmarks from Verizon DBIR 2026, Edgescan 2025, Bitsight 2024, and Qualys show that remediation often takes months, far exceeding regulatory requirements such as FSTEC Order 117. A five-level maturity ladder is presented, ranging from chaos to continuous CTEM, to help teams assess progress. The article concludes that simulated attacks and red team exercises provide the most honest validation of VM effectiveness beyond dashboard numbers.
WordPress Core Update RCE Vulnerability CVE-2026-119977 Actively Exploited, CISA Adds to KEV Catalog
The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has added a critical remote code execution flaw in WordPress to its Known Exploited Vulnerabilities catalog after confirming active exploitation in the wild. The vulnerability, tracked as CVE-2026-119977, resides in the core update mechanism and allows attackers to predict temporary file paths created during package updates, enabling unauthorized code execution from external sources. Wordfence assigned the flaw a CVSS v3.1 base score of 8.1 and reported blocking over 13,000 exploitation attempts targeting its customers within a single 24-hour period. The issue was addressed in the WordPress 7.1.4 release on October 28, 2026, with backports now being rolled out to all branches from version 4.7 onward. CISA has set a three-day remediation deadline of November 6, 2026, for U.S. federal agencies and instructed them to investigate potential compromises. Security researchers note that the attack leverages predictable temporary file locations during the update process, making it particularly dangerous for unpatched installations.
Barracuda ESG Hit by High-Severity Vulnerabilities Allowing Chained Root Access
Barracuda Networks has released patches for multiple products after disclosing two high-severity vulnerabilities that affect the Email Security Gateway (ESG). CVE-2026-116606 is a pre-authentication authorization bypass in ESG that permits an attacker with network access to the management interface to import a malicious backup file and alter device configuration without credentials. CVE-2026-111560 is an OS command injection flaw in timezone configuration handling that requires administrator login but grants root-level command execution. The command injection issue also impacts Load Balancer ADC, Message Archiver, WAF Control Center, Web Application Firewall, and Web Security Gateway. The vendor published its advisory on November 2, 2026, and urges immediate application of the fixes to prevent potential full system compromise through chained exploitation.