Google Patches Actively Exploited V8 Zero-Day in Chrome (CVE-2026-85046)
Google has distributed an urgent update for Chrome to correct CVE-2026-85046, a zero-day vulnerability in V8 that is being actively exploited. The solution requires updating to Chrome 152.0.7977.82 or higher and restarting the browser to apply the patch.
Google released the emergency update after detecting active exploitation of CVE-2026-85046, a high-severity zero-day in V8, the JavaScript and WebAssembly engine used by Chrome. The vulnerability enables a remote attacker to execute arbitrary code inside the browser sandbox when the victim visits a manipulated HTML page, a scenario typical in campaigns that combine malicious links, malvertising, or compromised websites.
The defect is classified as a type confusion in V8, a class of vulnerability that often provides dangerous primitives such as arbitrary read and write access within the JavaScript heap. Technical analysis points to the Maglev compiler and optimizations related to Array.prototype.sort, where certain inlining and specialization decisions can leave the engine in an inconsistent state that becomes exploitable.
Google has corrected 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 addresses a total of twelve vulnerabilities, reinforcing the recommendation to apply the patch as soon as possible.
The company continues its policy of limiting technical details on selected flaws until the majority of users have updated, aiming to slow further exploitation. Researcher Salvatore Gulizia, known as Serotav, reported the vulnerability on 4 August 2026 and received a $1,000 reward. The published CVSS score is 8.8, reflecting the requirement for user interaction consistent with web-based attacks.
For users, the practical mitigation is straightforward: update Chrome and restart the browser so the patched version is running. In enterprise environments it is advisable to accelerate patch management, verify deployed versions, and prioritize high-exposure systems. Administrators should also monitor Chromium-based browsers such as Microsoft Edge, Brave, Opera, and Vivaldi, which will need to incorporate the fix in their own release cycles.
Related articles
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.
WordPress Patches Race Condition in Core Update Process Enabling Unauthenticated Remote Code Execution
WordPress addressed a critical race condition vulnerability in its core update mechanism on October 28, 2026, that could allow remote code execution without authentication. The flaw affects the automatic update process used by the majority of installations, exposing a temporary installer during file extraction to a predictable folder. Wordfence recorded 60,471 exploitation attempts within the first 24 hours after disclosure. The issue was discovered by researcher Umut Bayram and fixed across multiple branches including version 7.1.4, which bundles 22 security patches. Mitigations include immediate updates, restricting public access to the wp-content update directory, and ensuring application firewall coverage. Versions 4.6 and earlier receive no further security updates.