On this page (7 sections)

A high-severity vulnerability, CVE-2026-133680, has been published for the D-Link DCS-935L network camera running firmware 1.10.01. According to the GitHub Advisory Database entry, a manipulation of the account or password argument in the Local Recording CGI results in OS command injection, it can be triggered remotely, and the exploit has been made public.

If you run one of these cameras at an office, shop, warehouse or a client site, this is worth acting on today. The advisory does not list a patched version, so the practical focus is on limiting exposure. Only one independent publisher covers this so far, and the NVD record repeats the same description.

What was reported

The advisory says the flaw affects the function loginRouter in web/cgi-bin/localrecording/setconf.cgi, part of the Local Recording CGI component. Manipulating the account or password argument leads to OS command injection. The record was published on November 20, 2026 and the NVD entry carries the same text.

The references include a public repository and several VulDB entries. The advisory states that the exploit has been made public and could be used. We have not reviewed those materials for this article and do not describe exploit details here.

Why command injection on a camera matters

OS command injection happens when a device passes user-supplied text into a system command without safely separating data from instructions. Whoever controls that text can make the device run commands of their choosing. On a small embedded camera that can mean control of the whole device.

The CVSS v4 metrics in the advisory describe network attack vector, low attack complexity, no user interaction, and low privileges required, with high impact on confidentiality, integrity and availability. In plain terms, an attacker who can reach the camera's web interface and holds a low-privilege login may be able to take it over. The privileges requirement is low rather than none, so the exact conditions for exploitation are not fully clear from the research.

Compromised cameras are commonly abused to view or alter video, to pivot into the local network, or to be enrolled in botnets. The research does not say any of this has happened with CVE-2026-133680, so treat these as general risks of device takeover, not confirmed activity.

Who is exposed

  • Any DCS-935L running firmware 1.10.01, which is the version named in the advisory.
  • Cameras whose web interface is reachable from the internet, for example through port forwarding or UPnP.
  • Cameras on flat networks where a compromised laptop or guest device could reach the camera directly.
  • Other DCS-935L firmware versions are not described in the research, so their status is unknown. Do not assume they are safe.

How to check your exposure

Start by finding out whether you have the device and which firmware it runs. Open the camera's admin page from inside your network and look at the firmware version in the device or status section. The exact menu name can differ, so check the D-Link documentation for your unit.

Next, check whether the camera is reachable from outside. From a machine outside your network (a mobile hotspot works), try to open the camera's public address and port. If it loads, it is exposed. Also review your router's port forwarding and UPnP lists for entries pointing at the camera.

This read-only command, run from a Linux or macOS machine on the same network, prints the HTTP response headers of the camera so you can confirm it is answering on its web port. Replace the placeholder with your camera's local address; a header response means the web interface is up.

Check that the camera web interface answers locally (read-only, run on your LAN)Shell
curl -sI http://CAMERA_IP_ADDRESS/

What to do now

There is no vendor fix listed in the research. Check the D-Link site for a security bulletin or firmware update for the DCS-935L, and be aware that the research does not say whether the model still receives updates. Until a fix is confirmed, reduce exposure.

  1. Inventory every DCS-935L you operate and note its firmware version.
  2. Remove any port forwarding or UPnP mapping that exposes the camera to the internet.
  3. If remote viewing is required, put the camera behind a VPN instead of publishing its web interface.
  4. Place cameras on a separate VLAN or guest network that cannot reach business systems.
  5. Change the camera's admin password to a long, unique one and remove unused accounts, which limits who holds the low-privilege login the advisory's metrics describe.
  6. Check D-Link's support pages for a firmware update and apply it if one is released, after reading its release notes.
  7. If the model is no longer supported and no fix appears, plan to replace it.
  8. Watch the camera and router for unexpected reboots, new outbound connections or changed settings, and factory reset and reconfigure any unit you suspect was tampered with.
Caution. Applying firmware or factory resetting a camera interrupts recording and may reset your settings. Do it in a maintenance window and back up the configuration first if the device allows it.

Detection and monitoring

Embedded devices rarely give good logs, so watch from the network side. Review firewall or router logs for inbound connections to the camera's web port from unfamiliar addresses, and for the camera initiating outbound connections it does not normally make. If your logs record request paths, repeated requests to the Local Recording CGI path from outside your network would be worth investigating.

If you run a website or other services at the same site, an outside-in view helps you spot what is publicly reachable. The Webforta scanner performs read-only scans of sites you verify, and Webforta Monitor tracks uptime, certificate and DNS changes. Neither inspects camera firmware or detects this specific flaw, so they complement, not replace, the network steps above.

What is still unknown

  • Whether a patched firmware version exists. The advisory lists patched versions as unknown.
  • Which other firmware versions are affected beyond 1.10.01.
  • Whether the flaw is being exploited in the wild. The research only says a public exploit exists, and the CVE is not in CISA KEV.
  • Whether D-Link has acknowledged the report. The research cites no D-Link advisory.

We will treat this as a developing story. For broader guidance on reducing exposure at the sites you run, see our guide on small business website security.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-133680 - GitHub Advisory Databasegithub.com
  2. CVE-2026-133680: A vulnerability was found in D-Link DCS-935L 1.10.01.nvd.nist.gov ·
  • D-Link
  • IP camera
  • command injection
  • CVE-2026-133680
  • IoT security