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
Critical PHP Vulnerabilities CVE-2026-109618 and CVE-2026-109619 Enable Unauthenticated Remote Code Execution
Two critical vulnerabilities in PHP, tracked as CVE-2026-109618 and CVE-2026-109619, both scoring CVSS 9.2, were disclosed on October 21. The flaws allow attackers to execute arbitrary code without authentication by triggering out-of-memory conditions that lead to use-after-free memory corruption. Exploitation involves specially crafted requests that manipulate uninitialized arrays and function pointers, with full chains demonstrated via PHP_SESSION_UPLOAD_PROGRESS and fatal error backtraces. The issues affect PHP versions starting from 5.4 and were discovered using AI tools Gemini 4 Argon and GPT-5.6 Sol, resulting in a patch exceeding 10,000 lines of code. Amazon detected attacks as early as October 17, with Cloudflare later reporting millions of exploitation attempts. Mitigation requires updating to patched versions such as PHP 8.2.35, 8.3.36, 8.4.27 or 8.5.12, while temporary workarounds include disabling session upload progress and fatal error backtraces.
Trend Micro ZDI Reports on Critical Linux KSMBD Vulnerabilities Leak to Public Mailing Lists Before Patches
Trend Micro Zero Day Initiative inadvertently published detailed vulnerability reports for the Linux kernel's KSMBD component into public mailing lists. Two flaws received CVSS scores of 9.0, enabling remote code execution under specific conditions. One issue involves a race condition during parallel SMB request handling, while the second stems from an incorrect buffer size calculation in the SMB Direct mechanism that requires RDMA and a writable share. Technical details including root causes and reproduction steps became publicly archived before fixes reached end users. The KSMBD maintainer has already merged a patch for ZDI-CAN-33774 into their repository, yet distribution kernels may still lack the update. Additional privilege-escalation and information-disclosure risks in other kernel components were also described in the leaked messages.
Node.js Issues Security Releases for 26.x, 24.x and 22.x Fixing High-Severity TLS and Brotli Flaws
Node.js published security updates on October 21, 2026 for the 26.x, 24.x and 22.x release lines. The patches address multiple high-severity vulnerabilities affecting TLS hostname validation and the Brotli decoder, along with updates to critical dependencies including OpenSSL and Undici. Several CVEs cover bypasses in certificate hostname checks when IP addresses use full-width digits or when hosts resolve loosely to IP addresses. A particularly serious out-of-bounds write in the Brotli decoder (CVE-2026-111497) could enable remote code execution on services processing compressed responses. Additional fixes resolve keep-alive socket timing issues, DNS resolution truncation with NUL characters, and entropy caching problems in crypto.randomUUID and randomInt functions. The releases also update c-ares, Undici, OpenSSL, SQLite and ca-cert bundles following the eMudhra intermediate CA compromise.
Atlassian October Security Bulletin Flags 176 Third-Party Library Vulnerabilities Across Jira, Confluence and Bitbucket
Atlassian released its October security bulletin detailing 176 vulnerability entries distributed across seven products including Jira, Confluence, Bamboo, Bitbucket, Crowd, Fisheye and Crucible. Of these, 162 entries carry high severity and 14 are rated critical, though the total does not represent 176 unique flaws because the same identifiers recur when multiple products share the same third-party library. All critical issues originate in external components rather than Atlassian code, with the most severe being CVE-2026-65637 in the Coyote component of Apache Tomcat used by Confluence, which allows interception of server-client connections. Affected versions and corresponding fixes were published for Confluence Data Center, Bamboo, Bitbucket Data Center, Jira Software and Jira Service Management, with the company stressing that administrators must compare exact build numbers against the full corrected-version table. No exploitation of the listed issues had been reported as of 22 October, and Atlassian classifies the inherited exposure from third-party libraries as lower priority, issuing separate critical alerts only for immediate-risk cases.