# CVE-2025-67186: Memory corruption in n/a

> Remote attackers can trigger a buffer overflow in the firewall module of TOTOLINK A950RG routers, potentially leading to arbitrary code execution or denial of service.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Feb 2026
- **Updated:** 4 Feb 2026
- **Also known as:** GHSA-xf8g-xrmp-prrv

## What is CVE-2025-67186?

CVE-2025-67186 is a critical memory corruption vulnerability in n/a, published on 3 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

TOTOLINK A950RG V4.1.2cu.5204_B20210112 contains a buffer overflow vulnerability in the setUrlFilterRules interface of /lib/cste_modules/firewall.so. The vulnerability occurs because the `url` parameter is not properly validated for length, allowing remote attackers to trigger a buffer overflow, potentially leading to arbitrary code execution or denial of service.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2025-67186?

It affects 1 product.


Products: Totolink A950rg Firmware.

## How do I fix CVE-2025-67186?

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

## Is CVE-2025-67186 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-67187](https://insights.sbomify.com/CVE-2025-67187/): Memory corruption in n/a (critical 9.8)
- [CVE-2025-67188](https://insights.sbomify.com/CVE-2025-67188/): Memory corruption in n/a (critical 9.8)
- [CVE-2025-45800](https://insights.sbomify.com/CVE-2025-45800/): Command injection in n/a (critical 9.8)
- [CVE-2022-25082](https://insights.sbomify.com/CVE-2022-25082/): Command injection in n/a (critical 9.8)
- [CVE-2022-36612](https://insights.sbomify.com/CVE-2022-36612/): Hardcoded credentials in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-67186 and fix it if it is affected.

What it is: CVE-2025-67186 is a critical memory corruption vulnerability in n/a, published on 3 Feb 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-2025-67186 exists.

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-2025-67186/ (Markdown: https://insights.sbomify.com/CVE-2025-67186/index.md)
```

## Sources

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

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