Skip to content
Fencer Intel
medium 4.2

CVE-2026-86586 json

Certain EZVIZ devices are affected by a replay attack vulnerability (CWE-294).

published yesterday modified yesterday also EUVD-2026-131413

cvss
4.2
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 15%
public exploits
0
none known

Summary

Certain EZVIZ devices are affected by a replay attack vulnerability (CWE-294). An attacker may intercept communication traffic and replay specific control commands, causing the device to execute unauthorized operations.

Is CVE-2026-86586 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-21).

CVSS scores

assigned by version score vector
CNA 3.1 4.2 CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

Affected products

  • EZVIZ CS-C6N-R101-1G2WF
    • versions below V5.3.8 build 260825
  • EZVIZ CS-TY1-R101-1G2WF
    • versions below V5.3.8 build 260825
  • EZVIZ CS-TY2-R101-1G2WF
    • versions below V5.3.8 build 260825
  • EZVIZ CS-H6c-R101-1G2WF
    • versions below V5.3.8 build 260825
  • EZVIZ CS-C6N-R101-1G2WF-KJDS
    • versions below V5.3.8 build 260825
  • EZVIZ CS-C6N-R101-1G2WF-KJ
    • versions below V5.3.8 build 260825
  • EZVIZ CS-TY1-B0-1G2WF-TIMBRO
    • versions below V5.3.8 build 260825
  • EZVIZ CS-C6N-B0-1G2WF
    • versions below V5.3.8 build 260825
  • EZVIZ CS-TY1-B0-1G2WF
    • versions below V5.3.8 build 260825
  • EZVIZ CS-TY2-B0-1G2WF
    • versions below V5.3.8 build 260825
  • EZVIZ CS-C6N-B0-1G2WF-Blk
    • versions below V5.3.8 build 260825
  • EZVIZ CS-C6N-B0-1G2WF-KJDS
    • versions below V5.3.8 build 260825
  • EZVIZ CS-H80f-R100-8G444WKFL
    • versions below V5.3.8 build 260903
  • EZVIZ CS-H7c-R101-8H44WF
    • versions below V5.3.8 build 260903

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.