CVE-2026-82987

waiting for further signalsZero needs more public information before it can validate it.

GHSA-r9hh-v5mm-mfgr ↗EUVD-2026-107560 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Viewsonic vCast >= v0.0.0, <= v3.2.715
ETK-2026-2360Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 40msince last run
23mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+0h48m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

vCast media streaming on affected ViewBoard devices exposes screen-capture functionality without authentication. A remote attacker able to reach the service may retrieve current screen content. Exposure depends on the vCast service being reachable by the attacker.

mitigation

Restrict vCast network access to trusted management networks and block untrusted access to the affected service. Disable vCast media streaming where it is not required, and monitor vendor guidance because no fixed version is recorded.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
23m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-21 20:48Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-21 20:48Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-82987

{
  "etk_id": "ETK-2026-2360",
  "cve_id": "CVE-2026-82987",
  "display_id": "CVE-2026-82987",
  "ghsa_id": "GHSA-r9hh-v5mm-mfgr",
  "euvd_id": "EUVD-2026-107560",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated screen capture exposure in vCast",
  "summary": "vCast media streaming on affected ViewBoard devices exposes screen-capture functionality without authentication. A remote attacker able to reach the service may retrieve current screen content. Exposure depends on the vCast service being reachable by the attacker.",
  "mitigation": "Restrict vCast network access to trusted management networks and block untrusted access to the affected service. Disable vCast media streaming where it is not required, and monitor vendor guidance because no fixed version is recorded.",
  "vendor": "Viewsonic",
  "product": "vCast",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= v0.0.0, <= v3.2.715"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "vCast",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 22.586541816666667,
  "t0_at": "2026-10-21T20:48:10.861000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-21T20:48:10.861000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-21T20:48:10.861000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-82987"
    }
  }
}

published 2026-10-21 21:13Z
last change 2026-10-21 23:06Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.