# CVE-2026-7247: D-Link DI-8100 File Extension file_exten.asp file_exten_asp buffer overflow

> Remote attackers can trigger a buffer overflow in the D-Link DI-8100 router's file extension handler, potentially leading to code execution or service disruption.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Apr 2026
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-8j59-4p62-3qc9

## What is CVE-2026-7247?

CVE-2026-7247 is a high-severity memory corruption vulnerability in D-Link DI-8100, published on 28 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability has been found in D-Link DI-8100 16.07.26A1. Affected by this issue is the function file_exten_asp of the file file_exten.asp of the component File Extension Handler. The manipulation of the argument Name leads to buffer overflow. Remote exploitation of the attack is possible. The exploit has been disclosed to the public and may be used.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Dlink Di-8100 Firmware.

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

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

## Is CVE-2026-7247 being exploited?

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

## Other vulnerabilities in D-Link DI-8100

- [CVE-2025-44083](https://insights.sbomify.com/CVE-2025-44083/): Auth bypass in n/a (critical 9.8)
- [CVE-2026-7853](https://insights.sbomify.com/CVE-2026-7853/): D-Link DI-8100 HTTP auto_reboot.asp sprintf buffer overflow (critical 9.3)
- [CVE-2026-7854](https://insights.sbomify.com/CVE-2026-7854/): D-Link DI-8100 POST Parameter url_rule.asp url_rule_asp buffer overflow (critical 9.3)
- [CVE-2026-7248](https://insights.sbomify.com/CVE-2026-7248/): D-Link DI-8100 CGI Endpoint tgfile.htm tgfile_htm buffer overflow (critical 9.3)
- [CVE-2026-7855](https://insights.sbomify.com/CVE-2026-7855/): D-Link DI-8100 HTTP Request tggl.asp tggl_asp buffer overflow (high 8.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7247 is a high-severity memory corruption vulnerability in D-Link DI-8100, published on 28 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7247 exists.

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

## Sources

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

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