CVE-2026-75619

MEDIUMPre-NVD 6.96.9
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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: secondary
Trending — 4 sources updated this week
6.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.9Exploit: None knownExposed: 0

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

Tapo C100/C101 V5 contains a heap-based buffer overflow vulnerability in the RTSP service. An authenticated attacker on the local network can send specially crafted RTSP frame data containing oversized length values, resulting in out-of-bounds heap writes.

Successful exploitation can crash the RTSP service and trigger a device reboot, resulting in a temporary denial-of-service condition.

CVSS v3
6.9
EG Score
6.9(low)
EG Risk
31(Track)
EG Risk 31/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
Severity69% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
12%
KEV
Not listed

Published

August 19, 2026

Last Modified

August 19, 2026

Advisory Details (4)

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

Security Advisory: Multiple Vulnerabilities in Tapo C100 and C101 (CVE-2026-75618 and CVE-2026-75619) | TP-Link

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

Vendor Advisories for CVE-2026-75619(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 7× in last 7d / 7× 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-20 22:56 UTCEPSS rescore
  2. 2026-08-20 19:01 UTCGHSA enrichment
  3. 2026-08-19 20:22 UTCEG score recompute
  4. 2026-08-19 19:44 UTCEG score recompute
  5. 2026-08-19 19:19 UTCEG score recompute
  6. 2026-08-19 18:38 UTCEG score recompute
  7. 2026-08-19 18:37 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-75619?
CVE-2026-75619 is a medium vulnerability published on August 19, 2026. Tapo C100/C101 V5 contains a heap-based buffer overflow vulnerability in the RTSP service. An authenticated attacker on the local network can send specially crafted RTSP frame data containing oversized length values, resulting in out-of-bounds heap writes. Successful exploitation can crash the RTSP…
When was CVE-2026-75619 disclosed?
CVE-2026-75619 was first published in the National Vulnerability Database on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-75619 actively exploited?
CVE-2026-75619 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 87.6% of all scored CVEs.
What is the CVSS score of CVE-2026-75619?
CVE-2026-75619 has a CVSS v3 base score of 6.9 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-75619?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-75619, 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-75619

Explore →

Is Your Infrastructure Affected by CVE-2026-75619?

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