D-Link DIR-505, CVE-2026-120189: a new CVE scored 10
The bottom line
Check whether you run D-Link DIR-505. If you do, read the vendor's page for the fixed version and update. Nothing public says yet that anyone is using this flaw.
At a glance
| Fact | Detail |
|---|---|
| Product | D-Link DIR-505 (CVE-2026-120189) |
| Severity | Critical: 10 (CVSS 4.0) |
| Status | A new CVE record, published by VulDB on 1 November 2026. Not on CISA's list of exploited vulnerabilities when we read it on 6 November 2026, which means nothing public says yet that anyone is using it. |
| Fixed in | No source we read names a fixed version |
| Who looks first | Anyone with a D-Link DIR-505 on firmware 1.10B02, and the IT provider who set it up. Check first for units reachable from the internet or from a network you do not fully trust. |
Does this apply to you?
| Question | If no | If yes |
|---|---|---|
| Do you run a D-Link DIR-505 anywhere, including at home offices or branches? | Nothing to do for this CVE. | Check the firmware version (next question). |
| Is the firmware version 1.10B02? | The record names only 1.10B02. Ask D-Link or your provider about other versions. | Check whether anyone untrusted can reach it. |
| Can the router's TFTP service be reached from the internet or an untrusted network? | Lower urgency, but plan to replace or update it. | Block that access first, then decide on replacement. |
What it is
The record says a flaw in the TFTP upload filename handler of the router's tftpd program causes a stack-based buffer overflow. It can be triggered remotely. The record does not say what an attacker gains, only the overflow.
What the vendor's advisory says
We read one page on github.com. In short:
- The only source we hold is a code repository directory listing with three file names. It is not a vendor advisory.
- No source names a fixed version, a workaround or a vendor statement.
Exposure by situation
These priorities are our judgement from what the sources say about who can use the flaw and how. They are not vendor ratings.
| Your situation | Priority | Timeframe |
|---|---|---|
| A DIR-505 on 1.10B02 that faces the internet | Medium | This week, before anything else |
| A DIR-505 on 1.10B02 reachable only from your internal network | Medium | This week or at the next maintenance window |
| A DIR-505 on a version other than 1.10B02 | Low | Next patch cycle, once the version's status is confirmed |
| No DIR-505 in your estate | None | None for this CVE |
Things people will get wrong
- "It is not on the CISA list, so nobody is attacking it." The record was new when read. Absence from the list means CISA has not recorded exploitation, not that nobody is trying. The record says the exploit is public.
- "There must be a patch to install." No source we hold names a fixed version. Do not assume one exists until the vendor says so in writing.
How we would triage it
This is our judgement.
Step 1: Find the DIR-505 units and their firmware
- List every DIR-505 you own, including remote and home-office units.
- Read the firmware version in the router's admin page. The record names 1.10B02 as affected.
Step 2: Reduce exposure
- Make sure the router's TFTP service and its administration pages are not reachable from the internet.
- The record says the attack can be carried out remotely, so exposure is the main factor.
Step 3: Ask the vendor about a fix
- No source names a fixed version. Ask D-Link or your provider whether one exists, and get the answer in writing.
- If none exists, plan to replace the unit.
Step 4: Confirm the result
- Record which units were found, their versions and what was changed.
- Ask your provider to confirm in writing that no affected unit is reachable from outside.
To close it, read the version from the product itself, not from an old inventory, and save the output with the date. If you cannot update today, write down who owns it, the new date, and what limits exposure until then.
Send this to your IT provider
Copy it, change the names and dates, and send it. It is a draft for you to check, not a template tested with any provider.
Hello, we are checking our exposure to CVE-2026-120189, a stack-based buffer overflow in the TFTP upload filename handler of the D-Link DIR-505, firmware 1.10B02. The record says it can be attacked remotely and that the exploit is public. Please tell us whether we run any DIR-505, where, and on which firmware. Please also confirm whether any can be reached from the internet, and whether D-Link has published a fix. Could you give us written confirmation of the versions and the action taken by the end of this week?
The weakness behind it
The record classes this as CWE-121 and CWE-119.
Likely ATT&CK mapping
MITRE ATT&CK is a public catalogue of the steps attackers take, from getting in to causing damage. No source has mapped this flaw to it yet, so the steps below are our prediction from what the record says the flaw allows. They are not MITRE's, the vendor's or CISA's, and an attacker may do other things.
| The step, in plain words | Stage of an attack | Why we think so |
|---|---|---|
| Exploit Public-Facing Application (T1190): Breaking in through a service that faces the internet, such as a web server, VPN or login page. | Initial Access: getting in | The overflow is in a TFTP service on a network-reachable router; an unauthenticated sender manipulating the upload filename would likely use this as the initial foothold without needing prior credentials. |
| Command and Scripting Interpreter (T1059): Running commands or scripts on a machine, such as a shell or PowerShell. | Execution: running the attacker's code | The public PoC uses a ROP chain to achieve remote code execution; a successful exploit would typically result in arbitrary commands running on the device's underlying operating system. |
| Exploitation for Privilege Escalation (T1068): Using a flaw to gain higher rights than the account had, such as administrator or root. | Privilege Escalation: gaining higher rights | TFTP daemons on embedded router firmware typically run with root privileges, so a successful overflow would likely elevate the attacker to full privileged execution in a single step. |
How to use this: ask your IT provider which control or log would show each step, for example whether sign-in attempts from the internet are recorded. If nobody can answer, that is the gap to close first.
MITRE ATT&CK® is a registered trademark of The MITRE Corporation. Technique names are MITRE's.
The sources, in their words
The CVE record:
A vulnerability was identified in D-Link DIR-505 1.10B02. Affected is the function save_upload_file/mp_upload_file of the file /usr/bin/tftpd of the component TFTP Upload Filename Handler. The manipulation leads to stack-based buffer overflow. The attack is possible to be carried out remotely. The exploit is publicly available and might be used.
Versions of D-Link DIR-505 the record lists as affected:
- 1.10B02
The record gives no version ranges. Use the vendor's advisory for the affected versions.
Check your own project
If you build software, you can compare what a project declares with this CVE from a terminal. The tool reads requirements files, package.json, Maven, Gradle, Cargo, CMake and Dockerfile files, runs nothing, and only the CVE id leaves your machine. Naming the CVEs needs no key.
lattice-scan project . --cve CVE-2026-120189Each row says in-range, outside-range, undetermined or lead, with the file and line. That is evidence about what a manifest declares, not about what runs, and a person decides. The verdicts, the CSV columns and a pipeline recipe are in the guide.
Check the servers you run
The same id can be checked against a host. Run this on the machine itself, not on the laptop that deploys to it: it reads installed packages (dpkg, rpm or apk), snaps, the hardware, the running container images with their operating system and packages, and the kernel version, compares them on the spot, and only the CVE ids leave the machine; the inventory stays on it, in ~/.lattice-scan. Naming the CVEs needs no key. Do it on each server after a deployment, and again when a new entry lands.
lattice-scan --cve CVE-2026-120189A match is a candidate for a person to confirm, not a finding. A distribution can fix a CVE under an unchanged version number, so a match is a candidate; on Debian-family hosts the report also shows whether the package's own changelog names the CVE. It reads the names of the running images, not what is inside them; for what an image declares, use the project check on its Dockerfile.
Guide: namiq.io/lattice/guides/choose-your-channel. MCP server (io.namiq/lattice in the MCP registry): namiq.io/lattice. Package: pypi.org/project/lattice-scan, or namiq.io/apt.
- Which way into Lattice fits your job →The command line, the Claude skill or the MCP server: what each needs, what works without a key and how to read the result.
- Lattice, the MCP server →The public graph the command reads, for AI agents over MCP.
- Install and connect →The signed apt repository, the fingerprint, and the connection commands for each client.
What we do not know yet
- Which firmware versions other than 1.10B02 are affected is not stated.
- No source names a fixed version or a workaround.
- The record does not say what an attacker gains beyond the overflow.
- Whether D-Link still supports this model is not stated.
- Exploitation is not recorded. That is not the same as none.
- This is a new record: scores, versions and wording can change in the first days, and they are as at 6 November 2026. We read the vendor pages listed under Sources; nothing here has been tested.
- The sections headed "Does this apply to you?", "What it is", "Exposure by situation", "Things people will get wrong", "Likely ATT&CK mapping", "How we would triage it" and "Send this to your IT provider" are our interpretation of the sources, not a statement by CISA or the vendor.