# CVE-2026-7554: D-Link M60 httpd password recovery

> Remote attackers can bypass password recovery mechanisms on D-Link M60 devices to potentially take over accounts.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/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:** 1 May 2026
- **Updated:** 4 May 2026
- **Also known as:** GHSA-j593-2446-m968

## What is CVE-2026-7554?

CVE-2026-7554 is a medium-severity vulnerability in D-Link M60, published on 1 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was determined in D-Link M60 up to 1.20B02. Affected by this issue is some unknown functionality of the file /usr/bin/httpd. This manipulation causes weak password recovery. The attack can be initiated remotely. A high degree of complexity is needed for the attack. The exploitation is known to be difficult. The exploit has been publicly disclosed and may be utilized.

Weakness: CWE-640 (Weak Password Recovery Mechanism for Forgotten Password)

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

It affects 1 product.


Products: Dlink M60 Firmware.

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

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

## Is CVE-2026-7554 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7554 is a medium-severity vulnerability in D-Link M60, published on 1 May 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-7554 exists.

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

## Sources

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

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