Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-4ghv-53cq-7wp3 | Home Assistant: mDNS Server-Side Request Forgery |
Fri, 25 Sep 2026 18:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 22 Sep 2026 22:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Home-assistant
Home-assistant core |
|
| Vendors & Products |
Home-assistant
Home-assistant core |
Tue, 22 Sep 2026 19:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Home Assistant: mDNS Server-Side Request Forgery | |
| Weaknesses | CWE-918 | |
| References |
|
|
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-09-24T15:25:00.416Z
Reserved: 2026-09-14T19:36:48.844Z
Link: CVE-2026-91129
Updated: 2026-09-24T15:24:40.359Z
Status : Awaiting Analysis
Published: 2026-09-22T19:16:56.433
Modified: 2026-09-25T14:10:13.927
Link: CVE-2026-91129
No data.
OpenCVE Enrichment
Updated: 2026-09-22T21:45:06Z
Github GHSA