Skip to main content
Menu
CVEs

Certain EZVIZ devices man-in-the-middle attacks via certificate validation flaw

CVE-2026-86587EUVD-2026-131412GHSA-45HV-PHRW-Q6FVPublished November 20, 2026, updated

5.3MediumCNA
Exploited
No known exploitation
Fix
See vendor advisory
Who is exposed
Not reported

Summary

Certain EZVIZ devices fail to properly validate certificates. An attacker on the same local network can intercept communication traffic and carry out a man-in-the-middle attack, without logging in or any user action.

Written by a model

Original description

Certain EZVIZ devices are affected by an improper certificate validation issue (CWE-295). An attacker may intercept communication traffic to conduct a man-in-the-middle attack.

What to do

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-86587 (Certain EZVIZ devices are affected by an improper certificate validation issue (CWE-295).), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-86587 (entry last updated 2026-11-20):
Affected:
- EZVIZ Certain EZVIZ devices: version range not reported
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-86587 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-86587 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.ezviz.com/inter/trust-center/security/security-notice/Improper%20Certificate%20Validation
- https://www.hikvision.com/en/support/cybersecurity/security-advisory/security-vulnerabilities-in-cloud-function-modules-of-some-hikvision-products/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-86587
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-86587"}.

Affected versions

cve.now Index

10Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure?/25Unknown. No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.3/10CVSS 5.3
  • No patch5/5No fixed version listed; see vendor advisory

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 32 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Evidence 4

No corrections so far. Something wrong on this page? Report an error.