Last updated: August 19, 2026 at 1:47 AM UTC
All 741 Vulnerability 286 Breach 129 Threat 319 Defense 7
Tag: browser-extension (3 articles)Clear

Adobe extension flaw let any website read a visitor's WhatsApp Web chats

Guardio Labs disclosed HermeticReader, a flaw chain in the Adobe Acrobat extension for Chrome that let an attacker controlled web page read data from a visitor's WhatsApp Web session. Tracked as CVE-2026-48294 and rated 7.4, it is a cross origin disclosure issue affecting versions up to 26.5.2.2, installed on roughly 329 million browsers. Any site could disguise commands as internal extension messages, activate the extension's WhatsApp integration, and redirect its privileged page operations into the WhatsApp tab, extracting chats, contacts, and message previews. No malware, stolen credentials, or WhatsApp flaw was involved. Adobe patched within days.

Check
Confirm the Adobe Acrobat Chrome extension is updated to 26.5.2.3 or later across managed browsers, and review which other extensions hold broad permissions across sensitive web applications.
Affected
Anyone running the Adobe Acrobat Chrome extension at version 26.5.2.2 or earlier with an active WhatsApp Web session (CVE-2026-48294); visiting a malicious page was enough to expose chats and contacts.
Fix
Update the extension, govern browser extensions with allow lists and permission reviews, and remember that a widely trusted extension can turn any visited page into a route to session data.

Popular ModHeader dev extension pulled after hidden history collector found

Google and Microsoft removed ModHeader, a header-editing browser extension popular with developers, with about 1.6 million installs, after researchers at Stripe OLT found a hidden browsing-history collector inside the official, signed store version. The collector was dormant, gated off by an empty allow-list, and no evidence has emerged that it ever sent data, but its presence in a trusted, signed extension is the concern. Its design frustrated automated review: the data was encrypted, the upload was switched off so sandboxes saw nothing leave, and malicious code was blended into a legitimate codebase, so scanners rated it low risk. It is a reminder that a store signature proves origin, not safe behavior.

Check
Check whether ModHeader is installed on developer or tester machines, remove or update it per the vendors' guidance, and review which browser extensions have broad permissions across your organization.
Affected
Developers and testers who installed ModHeader, and their organizations; a trusted, signed extension shipped a dormant collector capable of recording visited domains, showing signed extensions can still hide unwanted behavior.
Fix
Govern browser extensions with allow-lists and permission reviews, do not treat a store signature as proof of safe behavior, prefer minimal necessary extensions, and monitor for extensions contacting unfamiliar external endpoints.

Edgecution malicious Edge extension escapes the browser sandbox to plant a backdoor

Zscaler detailed Edgecution, a malicious Microsoft Edge extension used in ransomware-linked intrusions that abuses Chrome's native messaging feature, which normally lets extensions talk to desktop apps, to break out of the browser sandbox and run a Python backdoor on the host. The extension beacons to a command server and relays commands to the backdoor, giving attackers filesystem access and code execution, while running in a hidden headless browser to stay invisible. Attacks start with social engineering on Microsoft Teams, where the actor poses as IT support and directs employees to a fake "Outlook Updates" page. Researchers tie the activity to an access broker linked to the Payouts King ransomware operation.

Check
Review which browser extensions are installed across the organization and audit native messaging host registrations, and treat unsolicited Microsoft Teams messages from supposed IT support directing software installs as suspicious.
Affected
Organizations whose employees can install browser extensions and be reached by external Microsoft Teams messages; the technique escapes the browser sandbox to give attackers host-level access for ransomware staging.
Fix
Restrict browser extension installation through policy, control native messaging host configurations, lock down external Teams contact, and train staff to reject IT-support prompts pushing browser or software updates.