White Rabbitx 🏴☠️[verified]@TheRabbitPyPatch
The tweet announces critical CVEs CVE-2026-7363 and CVE-2026-7361, details the remote code execution vectors, and urges an immediate browser update to patch the vulnerabilities.
Lyrie.ai[verified]@lyrie_aiDisclosure
CVE-2026-7363, a critical use‑after‑free flaw in Chrome 147, was disclosed at 00:11 UTC; thirty patches have been issued to address the issue, though no PoC, exploit code, or evidence of active exploitation is provided.
IntegSec[verified]@integ_secDisclosure
The text announces CVE-2026-7363 as a use‑after‑free vulnerability in Chrome’s canvas API, discussing its business implications but offering no evidence of exploitation or existing patches.
Stuart 🇨🇷@stooee_General
The tweet highlights that CVE-2026-7363 has been widely reported, pointing to an external link for further information, but offers no technical or actionable details.
Aakash Rahsi@rahsi_aakaDisclosure
The tweet announces CVE-2026-7363, a use‑after‑free flaw in Chromium’s Canvas, linking to a post that likely contains a proof of concept, but does not mention any patch or active exploitation.
NerdieNews@NewsNerdieActive Exploitation
The tweet reports that CVE-2026-7363 is actively exploited in the wild, allowing remote code execution on Chrome with Canvas on Linux/ChromeOS, and urges users to apply the patch.
Vulmon Vulnerability Feed@VulmonFeedsDisclosure
The post discloses CVE-2026-7363, a use‑after‑free vulnerability in Chrome’s Canvas feature that affects versions before 147.0.7727.138.
CVE@CVEnewDisclosure
A new CVE-2026-7363 has been disclosed: a use‑after‑free in Chrome’s Canvas that allows remote code execution inside a sandbox on Linux/ChromeOS versions prior to 147.0.7727.138. No PoC, exploit, or patch information is mentioned.