CVE-2026-9770
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedKasa EC71 v4 and EC70 v4 firmware contains a static cryptographic private key stored in a read-only filesystem that is shared across devices. An attacker with access to the firmware image can extract the embedded key. Successful exploitation may allow an unauthenticated attacker on the same network to use this key in the web management service, compromising the confidentiality of encrypted communications. This may enable passive decryption of traffic or active man-in-the-middle (MITM) attacks
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Kasa EC71 v4 and EC70 v4 smart device firmware contains a hardcoded static RSA/SSH private key embedded in the read-only filesystem. This key is identical across all devices of these models. An attacker who obtains the firmware image can extract this key and use it to decrypt traffic or perform MITM attacks against any EC71/EC70 v4 device on the same network, since the web management service relies on this key for encrypted communications.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.4.0< 2.4.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify device model and hardware versionAccess the device management interface or check the physical device label to confirm the model is Kasa EC71 v4 or EC70 v4Affected if Device is NOT an EC71 v4 or EC70 v4 model - then not affected by this specific CVE
-
Determine firmware versionCheck the device settings page or use the Kasa mobile app to view the current firmware versionAffected if Unable to determine firmware version or version indicates older/unpatched firmware (compare against any vendor release notes for this CVE if available)
-
Verify web management service is accessibleConfirm the device has its web management interface enabled and reachable on the local network (typically on port 443 or 80)Affected if Web management service is disabled or not accessible - the attack requires network access to this service
-
Check network exposureDetermine if the device web interface is accessible from untrusted networks or if it is properly isolated on a local segmentAffected if Device web management is directly exposed to untrusted networks - increasing attack likelihood though the key still exists on the device regardless
-
Inspect firmware for embedded private keyIf firmware image is available (from vendor download or device extraction), search for RSA private key patterns (BEGIN RSA PRIVATE KEY, PEM format) or SSH private key patterns (BEGIN OPENSSH PRIVATE KEY) in the read-only filesystem portionAffected if Private key file or embedded key material is found in the firmware - confirms the hardcoded key vulnerability exists
Device is affected if it is a Kasa EC71 v4 or EC70 v4 with web management enabled and firmware containing the hardcoded static private key; the presence of that key in the firmware binary is the definitive indicator.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data2.4.0
Contact TP-Link for a firmware update addressing the hardcoded key; in the interim, isolate affected devices on a dedicated network segment and monitor for suspicious MITM behavior. The vendor must replace the static key with dynamically-generated per-device keys and push firmware updates to all affected units.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9770 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-9770 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data