CVE-2026-34123

HIGHPre-NVD 7.07.0
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 95% 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 — 3 sources updated this week
7.0EG
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.0Exploit: None knownExposed: 0

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

On Tapo C520WS v2, restricted accounts (for example, hub users) are intended to execute only a limited set of low‑sensitivity operations. Due to a logic flaw in the device’s API authorization mechanism, an attacker can craft requests that leverage legitimate “method mapping” behavior to bypass whitelist restrictions, allowing restricted operations to be masked as permitted requests and executed.

Successful exploitation may allow an attacker (with access to a restricted account) to execute unauthorized sensitive operations.  Depending on the operation invoked, impact could include device resets, unintended configuration changes, or disruption of normal operation, leading to loss of availability and integrity of the device.

CVSS v3
7.0
EG Score
7.0(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
Severity70% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

June 5, 2026

Last Modified

July 23, 2026

Advisory Details (3)

Auto-updated Jun 11, 2026
No patch confirmed yet.
generic

Security Advisory: Multiple Vulnerabilities on TP-Link Tapo C520WS (CVE-2026-6239, CVE-2026-6240, CVE-2026-6241, CVE-2026-6242, CVE-2026-34123)

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

Vendor Advisories for CVE-2026-34123(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 16× in last 7d / 59× 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.

Showing the most recent 100 of 144 total refreshes for this CVE.

  1. 2026-07-31 05:11 UTCEG score recompute
  2. 2026-07-31 05:11 UTCGHSA enrichment
  3. 2026-07-30 16:28 UTCEPSS rescore
  4. 2026-07-30 01:30 UTCEPSS rescore
  5. 2026-07-29 09:31 UTCEG score recompute
  6. 2026-07-29 09:31 UTCGHSA enrichment
  7. 2026-07-28 02:59 UTCEG score recompute
  8. 2026-07-28 02:59 UTCGHSA enrichment
  9. 2026-07-27 14:13 UTCEPSS rescore
  10. 2026-07-27 10:57 UTCGHSA enrichment
  11. 2026-07-26 21:51 UTCEG score recompute
  12. 2026-07-26 21:51 UTCGHSA enrichment
  13. 2026-07-26 07:19 UTCEG score recompute
  14. 2026-07-26 07:19 UTCGHSA enrichment
  15. 2026-07-25 14:18 UTCEPSS rescore
  16. 2026-07-25 14:18 UTCEPSS rescore
  17. 2026-07-24 14:17 UTCEPSS rescore
  18. 2026-07-24 14:17 UTCEPSS rescore
  19. 2026-07-23 14:18 UTCEPSS rescore
  20. 2026-07-23 14:18 UTCEPSS rescore
  21. 2026-07-23 03:09 UTCEG score recompute
  22. 2026-07-22 14:08 UTCEPSS rescore
  23. 2026-07-21 15:24 UTCEPSS rescore
  24. 2026-07-20 17:08 UTCEPSS rescore
  25. 2026-07-19 14:31 UTCEPSS rescore
Show 75 more
  1. 2026-07-19 02:29 UTCEPSS rescore
  2. 2026-07-18 10:04 UTCEPSS rescore
  3. 2026-07-16 17:03 UTCEPSS rescore
  4. 2026-07-16 11:54 UTCGHSA enrichment
  5. 2026-07-15 22:37 UTCGHSA enrichment
  6. 2026-07-15 16:57 UTCEPSS rescore
  7. 2026-07-15 16:57 UTCEPSS rescore
  8. 2026-07-15 02:00 UTCEPSS rescore
  9. 2026-07-14 16:05 UTCGHSA enrichment
  10. 2026-07-14 02:57 UTCGHSA enrichment
  11. 2026-07-13 22:30 UTCEPSS rescore
  12. 2026-07-13 06:13 UTCEPSS rescore
  13. 2026-07-13 06:13 UTCEPSS rescore
  14. 2026-07-12 05:46 UTCEPSS rescore
  15. 2026-07-12 00:15 UTCGHSA enrichment
  16. 2026-07-11 11:02 UTCGHSA enrichment
  17. 2026-07-11 08:27 UTCEPSS rescore
  18. 2026-07-10 21:54 UTCGHSA enrichment
  19. 2026-07-09 19:10 UTCEPSS rescore
  20. 2026-07-09 05:56 UTCGHSA enrichment
  21. 2026-07-08 16:54 UTCGHSA enrichment
  22. 2026-07-08 15:15 UTCEPSS rescore
  23. 2026-07-08 03:55 UTCGHSA enrichment
  24. 2026-07-07 13:46 UTCEPSS rescore
  25. 2026-07-06 16:27 UTCEPSS rescore
  26. 2026-07-06 16:27 UTCEPSS rescore
  27. 2026-07-05 18:11 UTCGHSA enrichment
  28. 2026-07-05 02:30 UTCEPSS rescore
  29. 2026-07-04 20:23 UTCGHSA enrichment
  30. 2026-07-04 06:31 UTCEPSS rescore
  31. 2026-07-03 16:35 UTCGHSA enrichment
  32. 2026-07-02 22:12 UTCGHSA enrichment
  33. 2026-07-02 09:13 UTCGHSA enrichment
  34. 2026-07-01 20:05 UTCGHSA enrichment
  35. 2026-07-01 15:06 UTCEPSS rescore
  36. 2026-07-01 07:06 UTCGHSA enrichment
  37. 2026-06-30 23:22 UTCEPSS rescore
  38. 2026-06-30 18:02 UTCGHSA enrichment
  39. 2026-06-29 21:25 UTCGHSA enrichment
  40. 2026-06-29 14:06 UTCEPSS rescore
  41. 2026-06-29 14:06 UTCEPSS rescore
  42. 2026-06-29 08:25 UTCGHSA enrichment
  43. 2026-06-28 17:09 UTCGHSA enrichment
  44. 2026-06-28 14:07 UTCEPSS rescore
  45. 2026-06-28 14:07 UTCEPSS rescore
  46. 2026-06-28 04:56 UTCEPSS rescore
  47. 2026-06-28 04:56 UTCEPSS rescore
  48. 2026-06-28 04:06 UTCGHSA enrichment
  49. 2026-06-27 15:06 UTCGHSA enrichment
  50. 2026-06-27 03:08 UTCEPSS rescore
  51. 2026-06-27 02:04 UTCGHSA enrichment
  52. 2026-06-26 12:56 UTCGHSA enrichment
  53. 2026-06-25 23:25 UTCGHSA enrichment
  54. 2026-06-25 13:49 UTCEPSS rescore
  55. 2026-06-25 13:49 UTCEPSS rescore
  56. 2026-06-25 10:25 UTCGHSA enrichment
  57. 2026-06-24 21:25 UTCGHSA enrichment
  58. 2026-06-24 14:05 UTCEPSS rescore
  59. 2026-06-24 08:21 UTCGHSA enrichment
  60. 2026-06-23 21:33 UTCEPSS rescore
  61. 2026-06-23 21:33 UTCEPSS rescore
  62. 2026-06-23 17:18 UTCGHSA enrichment
  63. 2026-06-22 22:55 UTCGHSA enrichment
  64. 2026-06-22 14:25 UTCEPSS rescore
  65. 2026-06-22 14:25 UTCEPSS rescore
  66. 2026-06-22 06:23 UTCGHSA enrichment
  67. 2026-06-21 14:56 UTCEPSS rescore
  68. 2026-06-21 14:56 UTCEPSS rescore
  69. 2026-06-21 11:53 UTCGHSA enrichment
  70. 2026-06-21 01:59 UTCEPSS rescore
  71. 2026-06-20 21:59 UTCGHSA enrichment
  72. 2026-06-20 08:16 UTCGHSA enrichment
  73. 2026-06-19 19:25 UTCEPSS rescore
  74. 2026-06-19 19:25 UTCEPSS rescore
  75. 2026-06-19 15:07 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-34123?
CVE-2026-34123 is a high vulnerability published on June 5, 2026. On Tapo C520WS v2, restricted accounts (for example, hub users) are intended to execute only a limited set of low‑sensitivity operations. Due to a logic flaw in the device’s API authorization mechanism, an attacker can craft requests that leverage legitimate “method mapping” behavior to bypass…
When was CVE-2026-34123 disclosed?
CVE-2026-34123 was first published in the National Vulnerability Database on June 5, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-34123 actively exploited?
CVE-2026-34123 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 95.2% of all scored CVEs.
What is the CVSS score of CVE-2026-34123?
CVE-2026-34123 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2026-34123?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-34123, 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-34123

Explore →

Is Your Infrastructure Affected by CVE-2026-34123?

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