CVE-2026-120189 D-Link DIR-505 TFTP Upload Filename tftpd mp_upload_file stack-based overflow
Critical 10.0
Published
Updated
Check this codebase for CVE-2026-120189 and fix it if it is affected.
What it is: CVE-2026-120189 is a critical vulnerability in D-Link DIR-505, published on 1 Nov 2026.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120189 exists.
Affected product: D-Link DIR-505. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-120189/ (Markdown: https://insights.sbomify.com/CVE-2026-120189/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-120189?
CVE-2026-120189 is a critical vulnerability in D-Link DIR-505, published on 1 Nov 2026.
Official description
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.
Which versions are affected by CVE-2026-120189?
How do I fix CVE-2026-120189?
No fix has been published for CVE-2026-120189 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-120189 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120189 exists.
Sources
Also known as GHSA-2j25-rfrh-cphw.