CVE-2026-133493

validatingZero is analyzing and reversing it now.
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-78 Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
ETK-2026-5016Zero's internal tracking ID, independent of the CVE number., permanent identifier
–running
startingcurrent stage
timeline
0 = cve.org publication
trigger signal (cve.org) +0h
0
+2h
+4h
+6h
+8h
+10h
+12h

description

D-Link DIR-600L firmware 2.17b02 is affected by an OS command injection flaw in the GENA Handler's gena.cgi component. A remote attacker may be able to execute operating-system commands by reaching the affected service; the evidence does not state whether authentication is required.

Still under analysis: more detail becomes available as the pipeline runs.

mitigation

Restrict management and GENA-related service access to trusted networks and block exposure from untrusted networks. Upgrade to vendor-provided corrected firmware when available; no fixed version is recorded in the advisory.

check
building now
exploit
not yet
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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
–
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-20 06: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

Run in progress: no artifact yet.

source signals

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

  1. 2026-11-20 06:45Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-5016",
  "cve_id": "CVE-2026-133493",
  "display_id": "CVE-2026-133493",
  "ghsa_id": null,
  "euvd_id": null,
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "OS command injection in D-Link DIR-600L GENA Handler",
  "summary": "D-Link DIR-600L firmware 2.17b02 is affected by an OS command injection flaw in the GENA Handler's gena.cgi component. A remote attacker may be able to execute operating-system commands by reaching the affected service; the evidence does not state whether authentication is required.",
  "mitigation": "Restrict management and GENA-related service access to trusted networks and block exposure from untrusted networks. Upgrade to vendor-provided corrected firmware when available; no fixed version is recorded in the advisory.",
  "vendor": "D-Link",
  "product": "DIR-600L",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "2.17b02"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "DIR-600L",
      "purl": null
    }
  ],
  "cwes": [
    78
  ],
  "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": null,
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": null,
  "t0_at": "2026-11-20T06:45:24.002000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-20T06:45:24.002000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-20T06:45:24.002000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-133493"
    }
  }
}

published 2026-11-20 07:24Z
last change 2026-11-20 07:24Z

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.