Medium · CVSS 5.4CVE-2026-102368

Plaintext Storage of a Device-Specific Private Key in Tapo S505 FirmwareCVE-2026-102368

Answer in brief

CVE-2026-102368 records a Medium severity (CVSS 5.4) vulnerability in Plaintext Storage of a Device-Specific Private Key in Tapo S505 Firmware. The current sources do not mark it as known exploited. The current feed maps TP-Link System Inc./Tapo S505 v1.6 (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Oct 8, 2026Updated Oct 8, 2026Source checked Oct 8, 2026First seen by HOL Oct 8, 2026Material review Oct 8, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 5.4
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 5.4. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps TP-Link System Inc./Tapo S505 v1.6 (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
TP-Link System Inc./Tapo S505 v1.6generic	>=0 <1.4.1 Build 260713	1.4.1 Build 260713, 1.4.1

Recommended response

Check inventory. Check lockfiles and deployed manifests for TP-Link System Inc./Tapo S505 v1.6.
Review the reported fix. Update TP-Link System Inc./Tapo S505 v1.6 to 1.4.1 Build 260713 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Oct 8, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Oct 8, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Oct 8, 2026

Sources and claim methodology

Upstream source description

Affected Tapo device firmware stores device-specific cryptographic material in plaintext within nonvolatile storage. An attacker with physical access to an affected device can recover this sensitive material from the firmware. Successful exploitation of this vulnerability may result in the disclosure of device-specific cryptographic material and could, under certain conditions, increase the risk of unauthorized access to related protected information or communications.

Quoted source text, attributed separately from HOL analysis.