CVE-2026-133993

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

GHSA-w3v9-27jf-mq5r ↗EUVD-2026-132550 ↗

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.
D-Link DIR-600L 2.17b02
CWE-121 Stack-based Buffer Overflow
ETK-2026-5152Zero's internal tracking ID, independent of the CVE number., permanent identifier
5h 26msince last run
30mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+0h40m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

D-Link DIR-600L firmware 2.17b02 is affected by a stack-based buffer overflow in its GENA subscription handler. An attacker who can reach the relevant service and submit a malformed service argument can trigger the flaw remotely.

mitigation

Restrict access to the router's network services to trusted internal hosts and block unsolicited inbound access from untrusted networks. No fixed version is recorded; monitor D-Link for an updated firmware release and apply it 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.
–
agent run time
30m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-21 17:45Z
Δ 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-21 17:45Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-5152",
  "cve_id": "CVE-2026-133993",
  "display_id": "CVE-2026-133993",
  "ghsa_id": "GHSA-w3v9-27jf-mq5r",
  "euvd_id": "EUVD-2026-132550",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Stack-based buffer overflow in D-Link DIR-600L GENA handler",
  "summary": "D-Link DIR-600L firmware 2.17b02 is affected by a stack-based buffer overflow in its GENA subscription handler. An attacker who can reach the relevant service and submit a malformed service argument can trigger the flaw remotely.",
  "mitigation": "Restrict access to the router's network services to trusted internal hosts and block unsolicited inbound access from untrusted networks. No fixed version is recorded; monitor D-Link for an updated firmware release and apply it when available.",
  "vendor": "D-Link",
  "product": "DIR-600L",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "2.17b02"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "DIR-600L",
      "purl": null
    }
  ],
  "cwes": [
    121
  ],
  "cvss_score": 10,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 29.8578099,
  "t0_at": "2026-11-21T17:45:12.399000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-21T17:45:12.399000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-21T17:45:12.399000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-133993"
    }
  }
}

published 2026-11-21 17:55Z
last change 2026-11-21 19:50Z

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.