# CVE-2026-2056: D-Link DIR-605L/DIR-619L DHCP Connection Status wan_connection_status.asp information disclosure

> Remote attackers can access sensitive information via the DHCP Connection Status handler in unsupported D-Link routers.

- **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
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Feb 2026
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-xj5p-hc38-q27c

## What is CVE-2026-2056?

CVE-2026-2056 is a medium-severity vulnerability in Dlink Dir-605l Firmware, published on 6 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A security vulnerability has been detected in D-Link DIR-605L and DIR-619L 2.06B01/2.13B01. The impacted element is an unknown function of the file /wan_connection_status.asp of the component DHCP Connection Status Handler. The manipulation leads to information disclosure. Remote exploitation of the attack is possible. The exploit has been disclosed publicly and may be used. This vulnerability only affects products that are no longer supported by the maintainer.

Weakness: CWE-284 (Improper Access Control), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 2 products.


Products: Dlink Dir-605l Firmware, Dlink Dir-619l Firmware.

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

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

## Is CVE-2026-2056 being exploited?

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

## Other vulnerabilities in Dlink Dir-605l Firmware

- [CVE-2021-40655](https://insights.sbomify.com/CVE-2021-40655/): D-Link DIR-605 Router Information Disclosure (high 7.5, exploited in the wild)
- [CVE-2026-42373](https://insights.sbomify.com/CVE-2026-42373/): D-Link DIR-605L B2 Hardcoded Telnet Backdoor Credentials (critical 9.8)
- [CVE-2023-29961](https://insights.sbomify.com/CVE-2023-29961/): Memory corruption in n/a (critical 9.8)
- [CVE-2023-24348](https://insights.sbomify.com/CVE-2023-24348/): Memory corruption in n/a (critical 9.8)
- [CVE-2023-24349](https://insights.sbomify.com/CVE-2023-24349/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-2056 is a medium-severity vulnerability in Dlink Dir-605l Firmware, published on 6 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-2056 exists.

Affected product: Dlink Dir-605l Firmware. 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-2056/ (Markdown: https://insights.sbomify.com/CVE-2026-2056/index.md)
```

## Sources

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

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