# CVE-2026-125079: D-Link DCS-6501LH Media Service SystemConfig.ini mydlink_default_sys_info hard-coded credentials


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-cwrm-p6wp-ch6h

## What is CVE-2026-125079?

CVE-2026-125079 is a medium-severity vulnerability in D-Link DCS-6501LH, published on 10 Nov 2026. 

### Official description

A vulnerability was determined in D-Link DCS-6501LH 3.03.02. This impacts the function pf_get_onvif_user_pwd/mydlink_default_sys_info of the file /mnt/conf/SystemConfig.ini of the component Media Service. This manipulation of the argument pin_code causes hard-coded credentials. It is possible to initiate the attack remotely. The exploit has been publicly disclosed and may be utilized.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-259 (Use of Hard-coded Password)

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


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

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

## Is CVE-2026-125079 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-125079 is a medium-severity vulnerability in D-Link DCS-6501LH, published on 10 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-125079 exists.

Affected product: D-Link DCS-6501LH. 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-125079/ (Markdown: https://insights.sbomify.com/CVE-2026-125079/index.md)
```

## Sources

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

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