Home Assistant Security Update Addresses 2 Vulnerabilities

P1 — VALIDATE AND UPDATEMedium to Critical · 5.4 / 9.3 (official CVSS v3/v4 scores)EXPLOITATION: NOT STATED

Quick Answer

Home Assistant has two separate fixes here. CVE-2026-91129 concerns IPP printer discovery and server-side requests initiated by a device on the local network; its listed fix is 2026.2.3. CVE-2026-91130 concerns script injection through names displayed in Statistics Graph tooltips; the reviewed advisory database maps its fix to 2026.7.0. Installing 2026.2.3 alone does not cover both. Select a supported release containing both fixes and confirm the served frontend is updated.

Confirm Scope And Apply The Supported Fix

What to do now: inventory Home Assistant Core and frontend versions, networks allowed to send discovery traffic, and integrations that supply entity names. Limit untrusted access to the discovery network and affected dashboards while updating. Preserve configuration and automation backups before the maintenance window.

Open the authoritative advisory

Source recheck: October 2, 2026 UTC. The linked project advisories were checked for this revision; deployment applicability and successful remediation still require local evidence. Recheck the supported release before changing production.

Scope And Authority

Product scopeHome Assistant packages and release streams identified in the project advisories
AdvisoryGHSA-4ghv-53cq-7wp3 / GHSA-wx4m-69m9-gx3m
CVEsCVE-2026-91129, CVE-2026-91130
Authoritative release date2026-09-16 UTC (project advisory dates, not database ingestion)
Authority revision date2026-09-16 UTC (project advisory dates, not database ingestion)
Affected versionsIPP SSRF: primary field <2026.2.2, with fix 2026.2.3; the intervening 2026.2.2 state is not resolved by that range.
Statistics Graph XSS: reviewed database lists <2026.7.0. The primary repository uses nonstandard range notation, so do not silently interpret it as a precise release interval.
Fixed versionIPP SSRF: 2026.2.3.
Statistics Graph XSS: 2026.7.0 according to the reviewed database; the upstream frontend change is PR 52235. These are issue-specific minimums, not a current complete security baseline.
CVSS base scoreIPP SSRF: 5.4 (v3.1) in the primary advisory. Statistics Graph XSS: 9.3 (v4) in the reviewed advisory database.
CVSS severityMedium to Critical
Exploitation statusNot stated by the authority; no exploitation claim is inferred.

What Changed

The IPP report requires a sender on the discovery network, but not prior printer setup or a Home Assistant login. Its redirect protection specifically rejects cross-origin redirects toward loopback or unspecified addresses; it is not a blanket ban on every private-network integration. The XSS path uses a malicious statistics entity name in an affected line-chart tooltip when a user hovers over a point. Such a name may arrive from an integration provider, so restricting local account creation alone does not remove that input path.

What To Validate Now

  1. Inventory. Record Core/frontend builds, discovery-network reachability, IPP integration use, Statistics Graph cards and providers that control entity names.
  2. Establish applicability. Evaluate the discovery and browser paths separately. Confirm the uncertain version boundaries with the project rather than declaring 2026.2.2 safe or treating an updated backend as proof of updated browser assets.
  3. Remediate. Use the supported installation-type update procedure for a release containing both fixes. Review integration compatibility and retain backups; do not downgrade to an old minimum solely because it appears in this table.
  4. Validate. In an isolated test instance, check discovery boundaries, escaped synthetic entity names and ordinary dashboard behavior. Verify loaded frontend assets and critical automations without triggering real locks, alarms or other physical actions.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

Use the exact supported release stream and repository. Test dependencies, clusters, integrations, and rollback before broad deployment; a CVSS rating or reachable feature is not evidence of exploitation.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.