CVE-2026-91129 json
Home Assistant: mDNS Server-Side Request Forgery
published last mo. modified last mo. also EUVD-2026-84804 , GHSA-4ghv-53cq-7wp3 , PYSEC-2026-4051
- cvss
- 5.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 22%
- public exploits
- 0
- none known
Summary
Home Assistant is open source home automation software focused on local control and privacy. Prior to 2026.2.3, the IPP integration automatically processed unauthenticated _ipp._tcp.local mDNS announcements in homeassistant/components/ipp/config_flow.py, where async_step_zeroconf passed attacker-controlled host, port, and base_path values to validate_input for printer metadata retrieval. Because the shared HTTP client followed attacker-controlled cross-origin redirects without blocking loopback targets, a local-network attacker could redirect the request to 127.0.0.1 or another internal service without user interaction or prior IPP configuration. This issue is fixed in version 2026.2.3.
Patch / fix
- pypi homeassistant 2026.2.3
- home-assistant home-assistant 2026.2.3
Is CVE-2026-91129 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- last mo.
Exploit prediction
0.29% chance of exploitation in the next 30 days, higher than 22% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- github.com https://github.com/home-assistant/core/security/advisories/GHSA-4ghv-53cq-7wp3 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N |
| GitHub | 3.1 | 5.4 | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N |
| OSV | 3.1 | 5.4 | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | homeassistant | <2026.2.3 |
2026.2.3 |
Affected products
- home-assistant core
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
References
-
github.com
/home-assistant/core/pull/162941
web
-
github.com
/home-assistant/core/commit/0f3c7ca2772b605c0f3c09c88f35e527ea6ea560
web
-
github.com
/home-assistant/core/commit/815c708d19aa0c7f59f9ee318b613a5e481a42b3
web
-
github.com
/home-assistant/core/security/advisories/GHSA-4ghv-53cq-7wp3
exploit, web
-
github.com
/home-assistant/core/releases/tag/2026.2.3
web
-
github.com
/home-assistant/core
package
-
pypi.org
/project/homeassistant
package
-
github.com
/advisories/GHSA-4ghv-53cq-7wp3
advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-91129
advisory
Sources
- CVE List CVE-2026-91129
- GitHub Advisory GHSA-4ghv-53cq-7wp3
- NVD CVE-2026-91129
- OSV PYSEC-2026-4051
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.