# CVE-2026-7219: Totolink N300RT formIpQoS buffer overflow

> Remote attackers can trigger a buffer overflow in the Totolink N300RT router via the formIpQoS interface, 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:** 29 Apr 2026
- **Also known as:** GHSA-rm9m-8jgv-m8g5

## What is CVE-2026-7219?

CVE-2026-7219 is a high-severity memory corruption vulnerability in Totolink N300RT, published on 28 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A flaw has been found in Totolink N300RT 3.4.0-B20250430. This affects an unknown function of the file /boafrm/formIpQoS. Executing a manipulation of the argument entry_name can lead to buffer overflow. The attack may be performed from remote. The exploit has been published 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-7219?


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

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

## Is CVE-2026-7219 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7219 is a high-severity memory corruption vulnerability in Totolink N300RT, 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-7219 exists.

Affected product: Totolink N300RT. 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-7219/ (Markdown: https://insights.sbomify.com/CVE-2026-7219/index.md)
```

## Sources

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

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