Loading story…
Two stored cross-site scripting (XSS) vulnerabilities, CVE-2026-33044 in the Map card and CVE-2026-33045 in the History-Graph card, were disclosed in Home Assistant. The flaws allow an attacker with low privileges to inject JavaScript that executes in an authenticated victim’s browser session when the affected dashboard content is viewed. Because the code runs with the victim’s permissions, attackers can steal session tokens, access browser local storage, and abuse authenticated REST API or WebSocket connections.
The impact can escalate from session hijacking to full administrative compromise when the victim has elevated privileges. Reported abuse paths include generating long-lived access tokens, creating new administrator accounts, changing passwords, altering system configurations, and disabling security integrations. The compromise may also extend beyond the application itself, potentially giving attackers control over connected smart home devices, alarm systems, and in some deployments the underlying host, with CVE-2026-33045 rated CVSS v4.0 7.3 and both issues described as high impact despite requiring user interaction.
See affected versions and whether adversaries are exploiting it.
1 event from the most recent confirmed update back to the earliest known activity.
Two stored cross-site scripting vulnerabilities affecting Home Assistant components were publicly documented: one in the Map card and one in the History-Graph card. The disclosures describe how injected JavaScript could execute in an authenticated user's browser and enable session hijacking, token theft, and potentially administrative compromise.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
2 references tracked. Mallory keeps watching after this page renders.
cvereports.com
Open sourcecvereports.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
ESPHome disclosed multiple vulnerabilities in its dashboard component that exposed authenticated users to arbitrary file access and stored cross-site scripting, with the most severe issue allowing remote attackers to read and write files under the configuration directory through the "edit configuration file" API. The path traversal flaw, tracked as **CVE-2024-27081** / `GHSA-8p25-3q46-8q2p`, affected version `2023.12.9` and could expose `esphome.json`, firmware source code, Wi-Fi credentials, fallback hotspot credentials, OTA passwords, and API encryption keys. In command-line installations, attackers could also modify Python scripts used during firmware compilation and flashing, creating a path to remote code execution on the host running the dashboard. A separate stored XSS bug, **CVE-2024-27287**, affected versions from `2023.12.9` through `2024.2.1` and stemmed from the `/edit` endpoint returning unsanitized user-controlled content as HTML. An authenticated attacker could inject JavaScript into a configuration file and trigger execution when another authenticated user opened a crafted `/edit?configuration=` link, enabling actions in the victim's session, access to sensitive data, configuration tampering, and firmware flashing on managed boards; the report also noted insufficient cookie protections that could aid session theft. ESPHome patched the file-write issue in version `2024.2.1` and the XSS issue in `2024.2.2`, and the advisories said chaining these flaws with additional weaknesses could lead to **unauthenticated remote code execution** against the machine hosting the dashboard.
Jun 29, 2026
Multiple high-severity vulnerabilities in **Open WebUI** allow attackers to plant malicious chat content that executes when viewed, leading to theft of JWTs and session tokens from `localStorage`, full account takeover, and compromise of sensitive AI assets. The flaws affect markdown rendering, citation and response iframe handling, and HTML file-serving paths, including cases where attacker-controlled content was rendered with dangerous HTML processing or iframe sandbox settings such as `allow-scripts allow-forms allow-same-origin`. Reported impacts include exposure of DOM data, `indexedDB`, cookies, backend API keys, model parameter files, private databases, and other enterprise AI resources. Several reports warn that if an administrator opens a malicious shared transcript or chat, the attack can escalate from stored XSS to **remote code execution** through Open WebUI's administrative features and Python-based functions or plugins, potentially yielding code execution on the Docker container or local host. The issues were addressed across releases including **v0.6.6** and **v0.7.0** by tightening file ownership checks, removing or making optional same-origin iframe access, and recommending stronger HTML sanitization and restrictive CSP settings; one report also provided a database query to hunt for stored chats containing suspicious `data:text/html` or `javascript:` embed payloads.
Jul 7, 2026
OpenReplay fixed a critical stored cross-site scripting flaw, tracked as **`CVE-2026-55879`**, that affects versions **`1.24.0` before `1.25.0`** and can let an unauthenticated attacker take over dashboard accounts. The issue allows anyone with a public project key to submit malicious custom event names or page URLs that are stored by the platform and later rendered in the authenticated dashboard, where attacker-controlled JavaScript can execute in the dashboard origin, steal the session JWT from `localStorage`, and hijack user access. The vulnerability is rated **CVSS 9.3** and mapped to **`CWE-79`**. The remediation shipped in **OpenReplay `v1.25.0`** and was reflected in subsequent code changes that centralized output encoding for event read paths. The patch escapes event entries and nested property maps on the backend before returning data from `SearchEvents` and `GetEventByID`, and also hardens the frontend by escaping JSON shown in `EventDetailsModal`, replacing `innerHTML` with `textContent` in a text measurement helper, and adding a reusable HTML-escaping utility. Together, the changes indicate the flaw stemmed from unsanitized event content being inserted into the UI without proper output encoding.
Jul 11, 2026