# CVE-2023-27482: Auth bypass in core

> Attackers can bypass authentication to access the Supervisor API in Home Assistant installations using affected Supervisor versions.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Mar 2023
- **Updated:** 25 Feb 2025
- **Also known as:** GHSA-2j8f-h4mr-qr25, ROOT-OS-ALPINE-319-CVE-2023-27482

## What is CVE-2023-27482?

CVE-2023-27482 is a critical authentication bypass vulnerability in home-assistant core, published on 8 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

homeassistant is an open source home automation tool. A remotely exploitable vulnerability bypassing authentication for accessing the Supervisor API through Home Assistant has been discovered. This impacts all Home Assistant installation types that use the Supervisor 2023.01.1 or older. Installation types, like Home Assistant Container (for example Docker), or Home Assistant Core manually in a Python environment, are not affected. The issue has been mitigated and closed in Supervisor version 2023.03.1, which has been rolled out to all affected installations via the auto-update feature of the Supervisor. This rollout has been completed at the time of publication of this advisory. Home Assistant Core 2023.3.0 included mitigation for this vulnerability. Upgrading to at least that version is thus advised. In case one is not able to upgrade the Home Assistant Supervisor or the Home Assistant Core application at this time, it is advised to not expose your Home Assistant instance to the internet.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2023-27482?

It affects 2 products.


Products: Home-Assistant Home-Assistant, Home-Assistant Supervisor.

## How do I fix CVE-2023-27482?

Upgrade to a fixed version.

## Is CVE-2023-27482 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-27482 exists.

Public exploit code:

- Home Assistant Supervisor - Authentication Bypass (nuclei): http/cves/2023/CVE-2023-27482.yaml

## Other vulnerabilities in home-assistant core

- [CVE-2023-41895](https://insights.sbomify.com/CVE-2023-41895/): Cross-site Scripting via auth_callback login in Home Assistant Core (high 8.8)
- [CVE-2023-41897](https://insights.sbomify.com/CVE-2023-41897/): Lack of XFO header allows clickjacking in Home Assistant Core (high 8.8)
- [CVE-2026-54317](https://insights.sbomify.com/CVE-2026-54317/): Home Assistant: Konnected alarm-panel switch state and zone topology disclosed to unauthenticated actors on the LAN (high 7.6)
- [CVE-2020-36517](https://insights.sbomify.com/CVE-2020-36517/): Information disclosure in n/a (high 7.5)
- [CVE-2018-21019](https://insights.sbomify.com/CVE-2018-21019/): Home Assistant information disclosure vulnerability (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-27482 and fix it if it is affected.

What it is: CVE-2023-27482 is a critical authentication bypass vulnerability in home-assistant core, published on 8 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-27482 exists.

Affected product: home-assistant core. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-27482/ (Markdown: https://insights.sbomify.com/CVE-2023-27482/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-27482
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-27482
- OSV: https://osv.dev/vulnerability/CVE-2023-27482

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-27482/
Summaries are generated and may contain mistakes; the official description above is the record.