⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Critical · CVSS 9.7

How to Fix CVE-2026-34205: Path Traversal in Home Assistant Operating System

Other vulnerabilities in the same area that are worth patching alongside this one:

*By Sai Kiran Pandrala*

⚡ At a glance
SeverityCVSS 9.7 - Critical
Actively exploited?Not currently listed in CISA KEV
Affected<= 17.1, < 2026.03.2
Fixed inSee vendor advisory
Type (CWE)CWE-923: Improper Restriction of Communication Channel to Intended Endpoints

What is CVE-2026-34205?

CVE-2026-34205 is a path traversal flaw in Home Assistant Operating System. The product fails to canonicalize or restrict file paths supplied by a remote caller, so .. sequences or absolute paths reach restricted parts of the filesystem. Vendor description: Home Assistant is open source home automation software that puts local control and privacy first. Home Assistant apps (formerly add-ons) configured with host network mode expose unauthenticated endpoints bound to the internal Docker bridge interface to the local network.

Why this CVE matters

Path traversal flaws look low-impact on paper but routinely chain into full compromise. An attacker who can read arbitrary files often pulls configuration secrets, session databases, or private keys, and many traversal bugs also allow writes that drop a webshell into the document root.

For deployments of Home Assistant Operating System that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Even where exploitation has not been publicly observed, scanning for the vulnerable fingerprint is cheap and routine. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

You are affected if your installation matches any of these version ranges:

Check your installed version against the list above. If you cannot determine the version, treat the system as affected and follow the upgrade path below.

Open Home Assistant Operating System's About dialog or run the vendor-documented version-check command. Compare the result against the affected ranges in the advisory.

How to fix CVE-2026-34205

  1. Read the vendor advisory in full: https://github.com/home-assistant/core/security/advisories/GHSA-gh5m-4m97-c95h
  2. Upgrade Home Assistant Operating System to the patched build listed in the vendor advisory.
  3. Back up the configuration (and database, where applicable) before upgrading.
  4. Apply the patch in a maintenance window. For HA pairs, upgrade the standby node first, fail over, then upgrade the former primary.
  5. Restart the affected service so the patched binary loads, then verify the new version (see verification section).

<!-- enrich-agent-8 -->

Pull and run the patched home assistant operating system container image (<patched-version>)

Vendor advisory: https://github.com/home-assistant/core/security/advisories/GHSA-gh5m-4m97-c95h


# Vendor advisory: https://github.com/home-assistant/core/security/advisories/GHSA-gh5m-4m97-c95h
# Pull the patched tag referenced in the advisory.
docker pull <registry>/home-assistant-operating-system:<patched-version>

# Restart the running container with the new image.
docker stop <container-name>
docker rm <container-name>
docker run -d --name <container-name> [...your usual flags...] <registry>/home-assistant-operating-system:<patched-version>

# Verify the image digest.
docker inspect <container-name> --format '{{.Image}}'


# Vendor advisory: https://github.com/home-assistant/core/security/advisories/GHSA-gh5m-4m97-c95h
# Same flow from Windows with Docker Desktop.
docker pull <registry>/home-assistant-operating-system:<patched-version>
docker stop <container-name>; docker rm <container-name>
docker run -d --name <container-name> <registry>/home-assistant-operating-system:<patched-version>

Verify the fix landed


# Vendor advisory: https://github.com/home-assistant/core/security/advisories/GHSA-gh5m-4m97-c95h
# 1. Confirm the running version matches the fixed-in version listed above.

# 2. Re-scan with your vulnerability scanner (Nessus, Qualys, Tenable, OpenVAS).
#    The scanner should no longer flag this CVE on the patched target.

# 3. Inspect recent service / kernel logs for crash-loops or rollback events.
journalctl -u <service> --since "10 minutes ago"
dmesg --since "10 minutes ago"

<!-- enrich-agent-8 -->

If you cannot patch immediately

Restrict access to the management interface to trusted internal IP addresses only. Block public access at the firewall and require VPN for any remote administration. Apply the patch as soon as a maintenance window allows.

How to verify the fix worked

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for unusually long URI paths containing traversal sequences, unexpectedly large responses from the affected endpoint, and outbound requests from the application to internal addresses or cloud-metadata endpoints. Treat any sensitive file the bug could disclose as exposed.

Frequently asked questions

Is CVE-2026-34205 being exploited in the wild?

Public exploitation has not been confirmed by CISA at the time of writing. Treat the patch as time-sensitive anyway; reports often lag actual abuse.

Will a WAF or IDS rule fully mitigate CVE-2026-34205?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

How long should I plan for the upgrade?

Typical vendor-documented upgrade windows for Home Assistant Operating System run from a few minutes to under an hour depending on cluster size. Test in a staging environment first and follow the vendor's documented HA upgrade order.

References

*This guide was assembled from the official vendor advisory, the NVD record, and the CISA KEV catalog entry on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*