CVE-2026-33044: Homeassistant Cross-Site Scripting Vulnerability

{
  "schema_version" : "1.4.0",
  "id" : "GHSA-r584-6283-p7xc",
  "modified" : "2026-03-27T21:48:32Z",
  "published" : "2026-03-27T20:33:22Z",
  "aliases" : [ "CVE-2026-33044" ],
  "summary" : "Home Assistant has stored XSS in Map-card through malicious device name",
  "details" : "### Summary\nAn authenticated party can add a malicious name to their device entity, allowing for Cross-Site Scripting attacks against anyone who can see a dashboard with a Map-card which includes that entity. It requires that the victim hovers over an information point (The lines or the dots representing that device's movement, as shown in the screenshot below, with the example showing a html-injection using `<s>` to strikethrough the text)\n<img width=\"348\" height=\"355\" alt=\"image\" src=\"https://github.com/user-attachments/assets/1af3ef33-3a72-4816-8ade-e6405aace176\" />\n\nThis allows an authenticated user to execute JavaScript in the context of any other users accessing a dashboard.\n\n### Details\n\nThe vulnerability exists in the map-card by adding a malicious entity and having the property `hours_to_show` set.\nSee example below, with the malicious entity being `Pixel 9 <s> Fold Robin {{7*7}}`:\nMap card with malicious device entity:\n<img width=\"338\" height=\"332\" alt=\"image\" src=\"https://github.com/user-attachments/assets/15229cc3-1b69-438c-9ee5-cbfa9483aec9\" />\n\nYAML-view of same card:\n<img width=\"338\" height=\"198\" alt=\"image\" src=\"https://github.com/user-attachments/assets/cd579266-75c3-4cdf-9d08-1544a6887feb\" />\n\n\nThis issue largely resembles the issue documented in: [CVE-2025-62172](https://github.com/home-assistant/core/security/advisories/GHSA-mq77-rv97-285m), but with an entity which can be displayed in a Map, instead of in an energy-dashboard.\n\n\n### PoC\n1. Register a new sensor (or device) or change the name of an existing one, which provides a location\n2. Change the name to something malicious, for example `test <img src=x onerror=alert(document.domain) />`\nFor a new entity, it should work when setting the name. For old entities, go here:\n<img width=\"1300\" height=\"411\" alt=\"image\" src=\"https://github.com/user-attachments/assets/d240549e-f26c-4617-89d7-5480451ae5a3\" />\n<img width=\"1383\" height=\"885\" alt=\"image\" src=\"https://github.com/user-attachments/assets/94db6186-ad54-476c-92a3-9f6870b0c862\" />\n<img width=\"387\" height=\"436\" alt=\"image\" src=\"https://github.com/user-attachments/assets/f4c4b9f6-b1e7-4b50-9012-3be31c617be4\" />\n<br>\n<img width=\"392\" height=\"515\" alt=\"image\" src=\"https://github.com/user-attachments/assets/a0f24d2f-cc18-4ef7-9071-40376dbb38c1\" />\n\n3. Add the entity to a map card, which has the \"hours to show\"-attribute set, to display movement history\n<img width=\"296\" height=\"383\" alt=\"image\" src=\"https://github.com/user-attachments/assets/b2db55b6-3d4b-4ab0-91fe-fc26813ad5ff\" />\n<img width=\"692\" height=\"410\" alt=\"image\" src=\"https://github.com/user-attachments/assets/aec15e07-12c0-4abf-ba73-979736131c7c\" />\n\n<img width=\"694\" height=\"302\" alt=\"image\" src=\"https://github.com/user-attachments/assets/e4bb7cac-fe85-41eb-963c-1743e78d937c\" />\n\n(The left arrow showing the custom setting, and the right arrow showing a data point which needs to be hovered)\n\n4. The payload executes when hovering a data-point (here shown with an \"alert(document.domain\"-payload)\n<img width=\"504\" height=\"118\" alt=\"image\" src=\"https://github.com/user-attachments/assets/9f24e1fe-949f-4fa5-9e4f-781828a1343b\" />\n\n### Impact\nThe impact of this vulnerability is that a user can target other users of the system and perform account takeover through client side exploitation of XSS.\n\nIn the context of this system, I believe the vulnerability to be less impactful than the CVSS metric describes, as it requires a specific setup (map-card with attribute `hours_to_show` set, as this brings up the trail). It is interesting to note that any user who sets this attribute, will be highly likely to trigger the vulnerability through normal use. It also has no potential for being imported through seemingly innocent integrations and can only be set explicitly by another invited user, a device name, a cloud service or through social engineering. Other devices which has the same sensor can trigger the same vulnerability, and I expect there to exists cloud-based devices that would enable a threat actor to deliver the payload remotely.\n\nSuggested criticality: **Medium**\n\nCredit: Robin Lunde - [https://robinlunde.com](https://robinlunde.com)",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:P"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "homeassistant"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2020.02"
      }, {
        "fixed" : "2026.01"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/home-assistant/core/security/advisories/GHSA-r584-6283-p7xc"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-33044"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/home-assistant/core"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-79", "CWE-80" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-27T20:33:22Z",
    "nvd_published_at" : "2026-03-27T20:16:30Z"
  }
}