CVE-2026-82159

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

GHSA-7m73-p97p-f9qj ↗EUVD-2026-116373 ↗

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.
Dell Wyse Management Suite < 2609.0.0.155
fixed in 2609.0.0.155
ETK-2026-3429Zero's internal tracking ID, independent of the CVE number., permanent identifier
1d 03h 23msince last run
19mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+4h59m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Dell Wyse Management Suite versions earlier than 2609.0.0.155 are affected by a cross-site scripting vulnerability. A remote user with low-privileged access may inject script content; exploitation requires that level of access to the management suite.

mitigation

Upgrade Dell Wyse Management Suite to version 2609.0.0.155 or later. Restrict remote access and low-privileged accounts until the upgrade is complete.

fixed in 2609.0.0.155

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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
19m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-03 20:50Z
Δ 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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-11-03 20:50Z
    ghsa: trigger signal, started the run
  2. 2026-11-03 20:50Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-3429",
  "cve_id": "CVE-2026-82159",
  "display_id": "CVE-2026-82159",
  "ghsa_id": "GHSA-7m73-p97p-f9qj",
  "euvd_id": "EUVD-2026-116373",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Cross-site scripting in Dell Wyse Management Suite",
  "summary": "Dell Wyse Management Suite versions earlier than 2609.0.0.155 are affected by a cross-site scripting vulnerability. A remote user with low-privileged access may inject script content; exploitation requires that level of access to the management suite.",
  "mitigation": "Upgrade Dell Wyse Management Suite to version 2609.0.0.155 or later. Restrict remote access and low-privileged accounts until the upgrade is complete.",
  "vendor": "Dell",
  "product": "Wyse Management Suite",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 2609.0.0.155"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2609.0.0.155"
      ],
      "package_name": "Wyse Management Suite",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 19.459121166666666,
  "t0_at": "2026-11-03T20:50:52.978000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-03T20:50:52.978000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-03T20:50:52.978000+00:00",
      "url": "https://github.com/advisories/GHSA-7m73-p97p-f9qj"
    }
  }
}

published 2026-11-04 01:30Z
last change 2026-11-04 21:53Z

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.