← back to feed
ETK-2026-2036Zero's internal tracking ID, independent of the CVE number.

ETK-2026-2036Zero's internal tracking ID, independent of the CVE number.

validatedZero produced an exploit or a check.
check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Broadcom Broadcom's version of Wi-Fi Protected Setup (WPS)
ETK-2026-2036Zero's internal tracking ID, independent of the CVE number., no cve assigned
−1.3dTTV
14mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal +0dcheck available+1.1dagent stopped
0
+2d

description

Broadcom devices using the affected Wi-Fi Protected Setup implementation may be vulnerable. An attacker close enough to communicate over Wi-Fi could execute code with root-level privileges on an affected router.

mitigation

Disable WPS on affected devices where configuration permits, and limit wireless access to trusted users and locations. Obtain and apply firmware updates from the device vendor when they become available.

check
available
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.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
14m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ 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 check: a technique exists and was validated, 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-19 06:29Z

this entry in the feed

GET /api/v1/feed/ETK-2026-2036

{
  "etk_id": "ETK-2026-2036",
  "cve_id": null,
  "display_id": "ETK-2026-2036",
  "ghsa_id": null,
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Remote code execution in Broadcom Wi-Fi Protected Setup",
  "summary": "Broadcom devices using the affected Wi-Fi Protected Setup implementation may be vulnerable. An attacker close enough to communicate over Wi-Fi could execute code with root-level privileges on an affected router.",
  "mitigation": "Disable WPS on affected devices where configuration permits, and limit wireless access to trusted users and locations. Obtain and apply firmware updates from the device vendor when they become available.",
  "vendor": "Broadcom",
  "product": "Broadcom's version of Wi-Fi Protected Setup (WPS)",
  "affected": [],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 13.573161066666668,
  "t0_at": null,
  "signals": {
    "check": {
      "at": "2026-10-20T08:05:05.816201+00:00",
      "days": -1.3027991502199074,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T15:21:07.719240+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-19T06:29:44+00:00",
      "days": -2.3690238747685184,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T15:21:07.719240+00:00",
      "url": "https://thehackernews.com/2026/10/unpatched-broadcom-wi-fi-flaw-lets.html"
    }
  }
}

published 2026-10-19 07:28Z
last change 2026-10-21 15:05Z

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.

Protected by reCAPTCHA; the Google Privacy Policy and Terms of Service apply.