Loading vulnerability…
CVE-2026-14382 is an insufficient validation of untrusted input vulnerability in ANGLE in Google Chrome prior to 150.0.7871.46. According to the provided content, a remote attacker could trigger the flaw via a crafted HTML page, leading to a potential browser sandbox escape. The issue is described by Chromium as High severity. The specific vulnerable function or code path is not provided in the available content; only that the flaw resides in the ANGLE component and stems from improper validation of attacker-controlled input processed during web content rendering.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
Repository contains a small native proof-of-concept for CVE-2026-14382, with two C programs and a README. The exploit is not network-facing; it is a local native graphics PoC that exercises EGL/OpenGL ES state transitions to trigger memory corruption in ANGLE-related transform feedback handling. The README states the bug is believed to be a variant of CVE-2025-6558 and includes a Chromium/ANGLE fix link, Android build commands, and a sample Android tombstone showing a SIGSEGV with execution flowing into /vendor/lib/egl/libGLES_mali.so. Structure: README.md documents the vulnerability, expected crash behavior, and build commands for arm32 and aarch64. poc.c is the main 32-bit PoC. It initializes an off-screen EGL pbuffer context, compiles minimal GLES 3 shaders, enables transform feedback on gl_Position, allocates a texture and transform feedback buffer, then performs a specific sequence: bind TF1, begin transform feedback, pause TF1, switch to TF2, redefine the still-referenced TF buffer through GL_ARRAY_BUFFER with a smaller size, perform buffer writes and a texture upload, switch back to TF1, resume transform feedback, and draw again. This sequence is intended to create stale/invalid state and trigger out-of-bounds or use-after-redefinition behavior in the graphics stack. poc64.c mirrors the same logic for aarch64 but is explicitly described as only demonstrating crashability; it loops through buffer redefinitions with varying sizes and resumes transform feedback, but does not achieve controlled PC. Capabilities: the code can reliably create an EGL/GLES environment, compile shaders, manipulate transform feedback objects and buffers, and trigger a crash in vulnerable graphics implementations. It does not include a post-exploitation payload, persistence, networking, or privilege-escalation logic. Overall maturity is PoC: it demonstrates vulnerability reachability and memory corruption/crash, with the 32-bit variant apparently closer to a controllable primitive, but it is not a weaponized exploit.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A specific vulnerability in the ANGLE component referenced in the Chrome 150 security fixes and highlighted as the highest-paid bug bounty in this release.
Specific vulnerability in the ANGLE component fixed in Chrome 150; highlighted as the most significant bug bounty item in the release notes excerpt.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.