Is CVE-2026-102368 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-102368 being exploited in the wild.

How severe is CVE-2026-102368?

Informational severity, published 8 October 2026.

Is there a fix for CVE-2026-102368?

Yes: fixed in 1.4.1 Build 260713. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-102368 attacked?

It is attacked with physical access, in a network appliance.

Am I affected by CVE-2026-102368?

Check whether you run TP-Link Tapo S505 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-102368: TP-Link Tapo S505 plaintext cryptographic key storage

CVE-2026-102368 · Severity: info · Published 2026-10-08

The Tapo S505 is a smart Wi-Fi light switch that stores device-specific cryptographic keys in plaintext within its firmware. An attacker with physical access to the device can extract these keys and potentially compromise communications or gain unauthorized access to connected systems. This vulnerability requires physical access to the hardware, limiting its immediate risk but creating a significant exposure for stolen or compromised devices.

Vendors: TP-Link.

Quick answers

Is CVE-2026-102368 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-102368 being exploited in the wild.
How severe is CVE-2026-102368?: Informational severity, published 8 October 2026.
Which products and versions are affected?: TP-Link Tapo S505 v1.6.
Is there a fix for CVE-2026-102368?: Yes: fixed in 1.4.1 Build 260713. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-102368 attacked?: It is attacked with physical access, in a network appliance.
Am I affected by CVE-2026-102368?: Check whether you run TP-Link Tapo S505 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 1.4.1 Build 260713

Technical details

The vulnerability is a cleartext storage of sensitive data flaw in the Tapo S505 firmware, where device-specific cryptographic material is stored unencrypted in nonvolatile storage. An attacker requires physical access to the device to extract and recover this material. Successful exploitation discloses the cryptographic keys, which could enable unauthorized access to protected communications or information depending on how the keys are used in the device ecosystem.

Affected products

TP-Link Tapo S505 v1.6

Timeline

2026-10-08: disclosed
2026-10-08: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.