Skip to main content
Menu
CVEs

D-Link DIR-600L remote command injection in GENA handler

CVE-2026-133493Published , updated

10.0CriticalCNA
Exploited
Proof of concept public, per CISA
Fix
See vendor advisory
Who is exposed
Not reported

Summary

The D-Link DIR-600L has an OS command injection flaw in the genacgi_main function of its gena.cgi file, in the GENA Handler component. A remote attacker can trigger it without logging in and run operating system commands on the device.

Written by a model

Original description

A vulnerability was identified in D-Link DIR-600L 2.17b02. Affected is the function genacgi_main of the file gena.cgi of the component GENA Handler. Such manipulation leads to os command injection. The attack can be launched remotely. The exploit is publicly available and might be used.

What to do

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-133493 (D-Link DIR-600L GENA gena.cgi genacgi_main os command injection), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-133493 (entry last updated 2026-11-20):
Affected:
- D-Link DIR-600L: versions 2.17b02
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133493 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133493 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://vuldb.com/vuln/440913
- https://vuldb.com/vuln/440913/cti
- https://vuldb.com/cve/CVE-2026-133493
- https://vuldb.com/submit/1049874
- https://www.dlink.com/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-133493
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133493"}.

Affected versions

cve.now Index

50Pof 100 · provisional · methodology v3
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity10/10CVSS 10.0, total technical impact per CISA
  • No patch5/5No fixed version listed; see vendor advisory

What would change the score

  • Would score about 80 if added to CISA KEV
  • Would score about 75 if CISA's SSVC rates exploitation active
  • Would score about 55 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now
  4. CISA SSVC assessment

    Exploitation: poc · Automatable: yes · Technical impact: total

  5. Record last updated

Evidence 8

Questions about CVE-2026-133493

Is CVE-2026-133493 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-133493?

DIR-600L: version 2.17b02.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.