# CVE-2026-94954: Memory corruption in n/a

> A stack-based buffer overflow in the TOTOLINK N150RT web interface allows attackers to execute arbitrary code or cause denial of service via crafted URL parameters.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 29 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-jmg7-x5hr-mqcm

## What is CVE-2026-94954?

CVE-2026-94954 is a high-severity memory corruption vulnerability in n/a, published on 29 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A stack-based buffer overflow vulnerability exists in the web management interface of TOTOLINK N150RT (NTR150) firmware V3.4.0-B20201030. It is reachable through the route /boafrm/formFilter (access-control / URL filter configuration handler) and is triggered by the url request parameter when the addFilterUrl (or addFilterUrlFlag) action flag is set.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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


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

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

## Is CVE-2026-94954 being exploited?

There is no known exploitation of CVE-2026-94954 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-94954 is a high-severity memory corruption vulnerability in n/a, published on 29 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-94954 in the wild and no public exploit code.

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

## Sources

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

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