Skip to content
IoT

CVE-2026-9770

8.6
High
EPSS 0.36%Patch availableJul 15, 2026

Static private key in Kasa EC70/EC71 v4 firmware allows traffic decryption and MITM.

common questions

Is CVE-2026-9770 being exploited?

Not confirmed. CVE-2026-9770 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.36% probability of exploitation in the next 30 days.

How severe is CVE-2026-9770?

CVE-2026-9770 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-2026-9770?

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

What does CVE-2026-9770 affect?

CVE-2026-9770 affects Kasa EC71 v4 firmware, Kasa EC70 v4 firmware. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-9770?

Apply vendor firmware update ASAP; isolate or replace affected devices if no patch.

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

executive summary
technical analysis
affected
Kasa EC71 v4 firmwareKasa EC70 v4 firmware
impact

Unauthenticated local attacker can extract embedded private key to decrypt web management traffic and perform MITM, compromising confidentiality.

action required

Patch when possible

affected versions
TP-Link Systems Inc. Kasa EC70 v4
  • affected< 2.4.0 Build 20260520 rel.4191
TP-Link Systems Inc. Kasa EC71 v4
  • affected< 2.4.0 Build 20260520 rel.4191

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