# CVE-2026-118579: D-Link DIR-505 Web Management CGI secmark1524.cgi main backdoor


- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-7h74-v9cc-6cp4

## What is CVE-2026-118579?

CVE-2026-118579 is a critical vulnerability in D-Link DIR-505, published on 28 Oct 2026. 

### Official description

A weakness has been identified in D-Link DIR-505 1.10B02. The impacted element is the function main of the file /secmark1524.cgi of the component Web Management CGI. This manipulation of the argument accu/pass/code/hash/cmds causes backdoor. The attack is possible to be carried out remotely. The exploit has been made available to the public and could be used for attacks.

Weakness: CWE-912 (Hidden Functionality)

## Which versions are affected by CVE-2026-118579?


## How do I fix CVE-2026-118579?

No fix has been published for CVE-2026-118579 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-118579 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-118579 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-118579 and fix it if it is affected.

What it is: CVE-2026-118579 is a critical vulnerability in D-Link DIR-505, published on 28 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-118579 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-118579/ (Markdown: https://insights.sbomify.com/CVE-2026-118579/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-118579
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-118579
- OSV: https://osv.dev/vulnerability/CVE-2026-118579

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-118579/
Summaries are generated and may contain mistakes; the official description above is the record.