CVE-2026-102159

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

GHSA-4pc8-pcf6-c2c3 ↗EUVD-2026-93956 ↗

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.
arista networks CloudVision CUE >= 2022.3.0, <= 2026.2.0
ETK-2026-817, permanent identifier
14d 15h 42msince last run
9mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+3h23m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

CloudVision CUE deployments with network-reachable backend services are affected by an access-control weakness. An unauthenticated attacker may invoke functionality intended for internal use, potentially exposing location information or disrupting services.

mitigation

Restrict network access to the CV-CUE backend so only authorized internal systems can reach it. Apply vendor-provided security updates when available.

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.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.36%28th percentile
agent run time
9m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-06 19:39Z
Δ 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

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

  1. 2026-10-06 19:39Z
    ghsa: trigger signal, started the run
  2. 2026-10-06 19:39Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-817",
  "cve_id": "CVE-2026-102159",
  "display_id": "CVE-2026-102159",
  "ghsa_id": "GHSA-4pc8-pcf6-c2c3",
  "euvd_id": "EUVD-2026-93956",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Access-control bypass in CloudVision CUE backend",
  "summary": "CloudVision CUE deployments with network-reachable backend services are affected by an access-control weakness. An unauthenticated attacker may invoke functionality intended for internal use, potentially exposing location information or disrupting services.",
  "mitigation": "Restrict network access to the CV-CUE backend so only authorized internal systems can reach it. Apply vendor-provided security updates when available.",
  "vendor": "arista networks",
  "product": "CloudVision CUE",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 2022.3.0, <= 2026.2.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "CloudVision CUE",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 9.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0036,
  "epss_percentile": 0.2875,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 9.206331066666667,
  "t0_at": "2026-10-06T19:39:53.582000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-06T19:39:53.582000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-06T19:39:53.582000+00:00",
      "url": "https://github.com/advisories/GHSA-4pc8-pcf6-c2c3"
    }
  }
}

published 2026-10-06 22:53Z
last change 2026-10-21 05:31Z

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.