Loading story…
Chromium issue trackers show two distinct browser security defects affecting separate components: a regular expression denial-of-service condition in DevTools and a heap-use-after-free bug in Blink's FontFeatureValuesMapIterationSource::FetchNextItem. The DevTools issue indicates a flaw that could allow specially crafted input to trigger excessive regular-expression processing and degrade browser responsiveness, while the Blink report points to a memory-safety error in font feature value iteration that can lead to unstable behavior and potential exploitation.
The reports highlight risk across both developer tooling and the rendering engine, with the Blink flaw standing out because use-after-free vulnerabilities in browser code are commonly scrutinized for possible code-execution impact. Although the available tracker entries provide limited public detail, the combination of a denial-of-service bug and a memory-corruption issue underscores ongoing exposure in Chromium components that are widely inherited by downstream browsers and applications.
See affected versions and whether adversaries are exploiting it.
2 events from the most recent confirmed update back to the earliest known activity.
A Chromium issue was published for a heap-use-after-free in blink::FontFeatureValuesMapIterationSource::FetchNextItem. The reference does not include further details on exploitation, impact, or a fix.
A Chromium issue tracking a Regular Expression Denial of Service vulnerability in DevTools was published. No additional technical details or remediation information are provided in the reference.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Chromium issue trackers document several security flaws affecting browser components including media parsing, graphics handling, extensions, and developer tooling. Reported issues include missing range validation for `second_chroma_qp_index_offset` in the H.264 PPS parser (`h264_parser.cc`), which could allow out-of-spec values to reach kernel GPU drivers; an out-of-bounds memory access in WebGL `texImage2D` tied to `UNPACK_IMAGE_HEIGHT`; and a use-after-free in `V8ConsoleAgentImpl::reportAllMessages`. A separate Chromium bug also references a security vulnerability in WebP, underscoring continued exposure in image and media processing paths. The reports also describe a privacy weakness in which browser extensions could infer full tab URLs through a side-channel involving `declarativeNetRequest`. Taken together, the disclosed bugs span memory corruption, insufficient input validation, and information leakage across high-risk surfaces commonly reachable through web content, browser extensions, and rendered media, with potential downstream impact that includes browser compromise, data exposure, or interaction with lower-level GPU driver code.
Jul 12, 2026
Microsoft published security advisories for two Chromium vulnerabilities affecting browser security components: **CVE-2026-5872**, a **use-after-free in Blink**, and **CVE-2026-5899**, an **incorrect security UI issue in History Navigation**. The flaws were listed in Microsoft's Security Update Guide as Chromium-related issues, indicating they affect browser code relied on by Microsoft products built on the Chromium engine. The Blink memory-safety bug could expose users to instability or potential exploitation scenarios typical of use-after-free vulnerabilities, while the History Navigation flaw involves incorrect security indicators that could mislead users about page state or trust signals during navigation. Organizations using Microsoft browsers or platforms that incorporate Chromium components should review the relevant advisories and apply the associated security updates through normal patch management processes.
Jul 12, 2026
A serious unpatched **Chromium** vulnerability was accidentally exposed after Google engineers marked the issue as fixed without shipping a patch, causing the bug report and proof-of-concept to become public. The flaw, originally reported in 2022, abuses the **Background Fetch API** to keep a Service Worker and malicious JavaScript running after the browser is closed and, in some cases, even after a device reboot. Affected products include **Chrome**, **Microsoft Edge**, **Brave**, **Opera**, **Vivaldi**, and **Arc**. The bug could let attackers abuse victims’ browsers for proxying traffic, launching DDoS activity, opening websites, and tracking user behavior; Google later re-hid the report and said it is working on a fix. Separately, researchers analyzing the **VoidStealer** infostealer found it can bypass Chrome’s **Application-Bound Encryption (ABE)** on Windows by attaching to the browser as a debugger, intercepting the moment Chrome decrypts protected data, and extracting the master key from memory. That technique enables theft of cookies, sessions, and other sensitive browser data, and the risk extends to other Chromium-based browsers using the same protection model. Together, the disclosures show that Chromium ecosystems face both browser-level persistence abuse and post-compromise data theft, with defenders urged to watch for unusual download-menu behavior, keep browsers updated as fixes arrive, and harden endpoints against infostealer activity.
Jun 29, 2026