# CVE-2025-15573: Missing Certificate Validation for Solax Power Pocket WiFi models MQTT Cloud Connection

> Attackers can intercept MQTT traffic to issue arbitrary commands to SolaX Power Pocket WiFi devices due to missing certificate validation.

- **Severity:** Critical 9.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Feb 2026
- **Updated:** 12 Feb 2026
- **Also known as:** GHSA-xp29-43pm-7r9g

## What is CVE-2025-15573?

CVE-2025-15573 is a critical vulnerability in SolaX Power Pocket WiFi 3.0, published on 12 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The affected devices do not validate the server certificate when connecting to the SolaX Cloud MQTTS server hosted in the Alibaba Cloud (mqtt001.solaxcloud.com, TCP 8883). This allows attackers in a man-in-the-middle position to act as the legitimate MQTT server and issue arbitrary commands to devices.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2025-15573?


## How do I fix CVE-2025-15573?

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

## Is CVE-2025-15573 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-15573 and fix it if it is affected.

What it is: CVE-2025-15573 is a critical vulnerability in SolaX Power Pocket WiFi 3.0, published on 12 Feb 2026. 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-2025-15573 exists.

Affected product: SolaX Power Pocket WiFi 3.0. 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-2025-15573/ (Markdown: https://insights.sbomify.com/CVE-2025-15573/index.md)
```

## Sources

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

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