Skip to content
IoT

CVE-2025-15573

9.4
Critical
EPSS 0.22%Feb 13, 2026

Certificate validation missing for MQTT TLS; MITM can issue commands.

common questions

Is CVE-2025-15573 being exploited?

Not confirmed. CVE-2025-15573 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.22% probability of exploitation in the next 30 days.

How severe is CVE-2025-15573?

CVE-2025-15573 is rated Critical with a CVSS score of 9.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2025-15573?

Not known from our data. No patch reference has been recorded for CVE-2025-15573, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2025-15573 affect?

CVE-2025-15573 affects SolaX Cloud MQTT-enabled devices, SolaX energy storage devices using MQTT TLS. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2025-15573?

Enable TLS cert validation; apply patch when released

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
SolaX Cloud MQTT-enabled devicesSolaX energy storage devices using MQTT TLS
impact

MITM on TLS MQTT allows attacker to issue arbitrary commands to devices.

action required

Patch when possible

affected versions
SolaX Power Pocket WiFi 3.0
  • affected< 3.022.03
SolaX Power Pocket WiFi 4.0
  • affected< 003.03
SolaX Power Pocket WiFi+4GM
  • affected< 1.005.05
SolaX Power Pocket WiFi+LAN
  • affected< 1.009.02
SolaX Power Pocket WiFi+LAN 2.0
  • affected< 006.06

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free