Loading vulnerability…
CVE-2026-4444 is a high-severity stack buffer overflow vulnerability in the WebRTC component of Google Chrome prior to version 146.0.7680.153. The flaw can be triggered by a remote attacker through a crafted HTML page, leading to stack corruption in the browser process. As a memory corruption issue in a remotely reachable browser component, the vulnerability may be exploitable for arbitrary code execution in the context of the targeted Chrome process.
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.
This repository is a small self-contained demonstration of JWT authentication bypass via attacker-controlled 'kid' header injection, labeled as CVE-2026-4444. It contains two code files: a vulnerable Node.js server (jwt_server.js) and a Python exploit (exploit_jwt_kid.py), plus a README and license. The vulnerable server exposes POST /api/verify on port 3000, decodes an incoming JWT, reads decoded.header.kid, and if the kid begins with http:// or https:// it fetches a public key from that URL using axios. It then verifies the token with jsonwebtoken while allowing RS256 and HS256. This creates a trust-boundary failure and SSRF-like key retrieval behavior because the attacker controls the key source. The Python exploit is operational rather than just illustrative: it starts an HTTP server on 0.0.0.0:8888 that returns a JSON object containing an attacker-controlled public key, forges a JWT signed with the matching private key, sets the JWT header kid to http://attacker.com:8888/key, and submits the token to http://localhost:3000/api/verify. If the target can reach the attacker-controlled URL and accepts the fetched key, the result is successful impersonation of the hardcoded subject 'admin'. The repository's purpose is educational/PoC-style demonstration of JWT key confusion and unsafe remote key lookup, showing both the vulnerable implementation and the exploit path end-to-end.
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.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A high-severity stack buffer overflow vulnerability in Chrome's WebRTC component.
One of multiple Palo Alto Networks product vulnerabilities listed in the advisory; no specific technical detail provided in the content 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.