# CVE-2026-72581: duhow xiaoai-patch - Server-Side Request Forgery in /auth Endpoint

> Remote attackers can force Xiaomi smart speakers to make arbitrary HTTP requests, enabling internal network scanning and access to internal services.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-mxx3-r9xg-4hf6

## What is CVE-2026-72581?

CVE-2026-72581 is a high-severity server-side request forgery vulnerability in duhow xiaoai-patch, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A server-side request forgery (SSRF) vulnerability in duhow/xiaoai-patch through commit fb07049 allows a remote attacker to make the Xiaomi smart speaker perform HTTP requests to arbitrary internal or external URLs. The /auth endpoint in api/main.py uses the user-supplied url POST parameter to redirect to a Home Assistant instance without validating the destination URL, enabling internal network scanning and access to internal services.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-72581?


## How do I fix CVE-2026-72581?

No fix has been published for CVE-2026-72581 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-72581 being exploited?

There is no known exploitation of CVE-2026-72581 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72581 and fix it if it is affected.

What it is: CVE-2026-72581 is a high-severity server-side request forgery vulnerability in duhow xiaoai-patch, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-72581 in the wild and no public exploit code.

Affected product: duhow xiaoai-patch. 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-2026-72581/ (Markdown: https://insights.sbomify.com/CVE-2026-72581/index.md)
```

## Sources

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

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