Skip to content
IoT

CVE-2025-15587

8.6
High
EPSS 0.18%Patch availableMar 16, 2026

Low-privilege can read admin password from Tinycontrol devices via direct resource.

common questions

Is CVE-2025-15587 being exploited?

Not confirmed. CVE-2025-15587 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.18% probability of exploitation in the next 30 days.

How severe is CVE-2025-15587?

CVE-2025-15587 is rated High with a CVSS score of 8.6. 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-15587?

Yes. A fix has been recorded for CVE-2025-15587. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2025-15587 affect?

CVE-2025-15587 affects Tinycontrol tcPDU, Tinycontrol LK3.5/LK3.9/LK4 LAN Controllers. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2025-15587?

Update firmware to fixed versions per device family.

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

executive summary
technical analysis
affected
Tinycontrol tcPDUTinycontrol LK3.5/LK3.9/LK4 LAN Controllers
impact

Attacker can read admin password via a non-UI resource, enabling credential access and potential device takeover.

action required

Patch when possible

affected versions
tinycontrol Lan Kontroler v3.5
  • affected< 1.67
tinycontrol LK3.9
  • affected< 1.75
tinycontrol LK4
  • affected< 1.38
tinycontrol tcPDU
  • affected< 1.36

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