# CVE-2026-4555: D-Link DIR-513 boa formEasySetTimezone memory corruption

> Remote attackers can exploit a stack-based buffer overflow in the D-Link DIR-513 router's timezone setting to execute arbitrary code or cause denial of service.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Mar 2026
- **Updated:** 23 Mar 2026
- **Also known as:** GHSA-fwg7-xgp7-84j9

## What is CVE-2026-4555?

CVE-2026-4555 is a high-severity memory corruption vulnerability in D-Link DIR-513, published on 22 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A weakness has been identified in D-Link DIR-513 1.10. The impacted element is the function formEasySetTimezone of the file /goform/formEasySetTimezone of the component boa. This manipulation of the argument curTime causes stack-based buffer overflow. The attack can be initiated remotely. The exploit has been made available to the public and could be used for attacks. This vulnerability only affects products that are no longer supported by the maintainer.

Weakness: CWE-121 (Stack-based Buffer Overflow), CWE-787 (Out-of-bounds Write), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Dlink Dir-513 Firmware.

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

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

## Is CVE-2026-4555 being exploited?

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

## Other vulnerabilities in D-Link DIR-513

- [CVE-2025-70229](https://insights.sbomify.com/CVE-2025-70229/): Memory corruption in n/a (critical 9.8)
- [CVE-2025-70230](https://insights.sbomify.com/CVE-2025-70230/): Memory corruption in n/a (critical 9.8)
- [CVE-2025-70231](https://insights.sbomify.com/CVE-2025-70231/): Path traversal in n/a (critical 9.8)
- [CVE-2025-70232](https://insights.sbomify.com/CVE-2025-70232/): Memory corruption in n/a (critical 9.8)
- [CVE-2025-70233](https://insights.sbomify.com/CVE-2025-70233/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-4555 is a high-severity memory corruption vulnerability in D-Link DIR-513, published on 22 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-4555 exists.

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

## Sources

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

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