Skip to content
IoT

CVE-2025-11500

8.7
High
EPSS 0.27%Patch availableMar 16, 2026

Unauthenticated local attacker can obtain interface credentials.

common questions

Is CVE-2025-11500 being exploited?

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

How severe is CVE-2025-11500?

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

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

What does CVE-2025-11500 affect?

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

What should I do about CVE-2025-11500?

Update to fixed firmware: tcPDU 1.36; LK3.5 1.67; LK3.9 1.75; LK4 1.38.

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

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

Exposes usernames and encoded passwords for the interface management portal via HTTP response when the secondary auth is off, enabling admin access.

action required

Immediate action required

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