dbcve.org
Cleartext TransmissionWeakness · CWE-319

CVE-2026-55844

HIGH · 7.5 CVSS v3.1 Published 2026-06-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Home Assistant is open source home automation software that puts local control and privacy first. Prior to 2025.5.0, The iOS companion app ignores the SSID allowlist for internal networks. The app uses SSID to detect when to use the internal URL, but whenever the app cannot find any other URL to be used, it fallbacks to the internal URL as well, which can expose user's token when connected to a not secure network. This vulnerability is fixed in 2025.5.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Home Assistant iOS companion app uses SSID detection to determine when to use internal URLs for local network communication. However, when no other URL is available, the app incorrectly falls back to the internal URL even when connected to networks not on the configured SSID allowlist. This causes user authentication tokens to be transmitted over untrusted networks, enabling potential token theft via man-in-the-middle attacks.

MitigationUpgrade the Home Assistant iOS companion app to version 2025.5.0 or later, which enforces SSID allowlist validation before using internal URLs. If unable to upgrade immediately, avoid connecting to untrusted WiFi networks while using the app.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Home Assistant iOS app version
    Open the App Store, go to your profile, find the Home Assistant app in Purchased or Updates, or open the app and navigate to Settings > About to see the version number
    Affected if The installed version is earlier than 2025.5.0 and the SSID allowlist feature is in use
  2. Verify SSID allowlist configuration in Home Assistant
    Open Home Assistant web interface, go to Settings > Mobile App > Companion App, look for SSID-based URL configuration or the 'SSID Allowlist' setting under the iOS device settings
    Affected if SSID allowlist is configured with specific network names
  3. Check current WiFi network connection on iOS device
    On the iOS device, go to Settings > Wi-Fi to see the currently connected network name (SSID)
    Affected if The device is connected to a WiFi network that is NOT in the configured SSID allowlist
  4. Inspect URL resolution behavior
    Use the iOS Companion app while connected to an untrusted network; examine network traffic or check the app logs/developer tools to see if internal URL (local IP/hostname) is being used instead of external/cloud URL
    Affected if The app resolves to an internal/local URL (e.g., http://192.168.x.x or http://homeassistant.local) when connected to a network outside the SSID allowlist

You are affected if running a Home Assistant iOS companion app version before 2025.5.0, with SSID allowlist configured, and the app incorrectly uses internal URLs while connected to WiFi networks not on the allowlist.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade the Home Assistant iOS companion app to version 2025.5.0 or later, which enforces SSID allowlist validation before using internal URLs. If unable to upgrade immediately, avoid connecting to untrusted WiFi networks while using the app.

Recommended fix High confidence

2025.5.0

  1. Upgrade the Home Assistant iOS companion app to version 2025.5.0 or later
  2. After upgrading, verify that the SSID allowlist is properly enforced for internal network detection

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-55844 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-55844 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data