CVE-2026-15316

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 91% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 4 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

An improper input validation vulnerability in the configuration service for processing encrypted credential data has been identified in Tapo C200 v5.  An attacker can send oversized crypted ciphertext values that may trigger exception handling failures, due to insufficient validation, causing the affected device to crash or restart.

Successful exploitation may temporarily disrupt HTTPS management and monitoring functionality, resulting in a denial-of-service (DoS) condition until the service recovers.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
32(Track)
EG Risk 32/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
9%
KEV
Not listed

Published

August 18, 2026

Last Modified

August 20, 2026

Advisory Details (3)

Auto-updated Aug 18, 2026
No patch confirmed yet.
generic

Security Advisory: Multiple Vulnerabilities in Tapo C200 (CVE-2026-15315 & CVE-2026-15316) | TP-Link

https://www.tp-link.com/us/support/faq/5248/
generic

Download for Tapo C200 | TP-Link

https://www.tp-link.com/us/support/download/tapo-c200/v5/
generic

Download for Tapo C200 | TP-Link

https://www.tp-link.com/en/support/download/tapo-c200/v5/

Vendor Advisories for CVE-2026-15316(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 15× in last 7d / 15× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 04:51 UTCEG score recompute
  2. 2026-08-21 04:51 UTCGHSA enrichment
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-20 16:38 UTCEG score recompute
  5. 2026-08-20 16:38 UTCGHSA enrichment
  6. 2026-08-20 15:46 UTCEG score recompute
  7. 2026-08-20 15:46 UTCGHSA enrichment
  8. 2026-08-20 11:06 UTCGHSA enrichment
  9. 2026-08-19 22:53 UTCEG score recompute
  10. 2026-08-19 22:53 UTCGHSA enrichment
  11. 2026-08-19 17:03 UTCEPSS rescore
  12. 2026-08-19 10:39 UTCGHSA enrichment
  13. 2026-08-18 22:23 UTCEG score recompute
  14. 2026-08-18 21:38 UTCEG score recompute
  15. 2026-08-18 21:38 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-15316?
CVE-2026-15316 is a high vulnerability published on August 18, 2026. An improper input validation vulnerability in the configuration service for processing encrypted credential data has been identified in Tapo C200 v5. An attacker can send oversized crypted ciphertext values that may trigger exception handling failures, due to insufficient validation, causing the…
When was CVE-2026-15316 disclosed?
CVE-2026-15316 was first published in the National Vulnerability Database on August 18, 2026, with the most recent update on August 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15316 actively exploited?
CVE-2026-15316 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 91.3% of all scored CVEs.
What is the CVSS score of CVE-2026-15316?
CVE-2026-15316 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-15316?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15316, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-15316

Explore →

Is Your Infrastructure Affected by CVE-2026-15316?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs