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

> An authenticated stack overflow in ALFA routers allows attackers to execute arbitrary code or escalate privileges via the torrentsindex parameter.

- **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:** 8 May 2025
- **Updated:** 13 May 2025
- **Also known as:** GHSA-765g-9g68-wg84

## What is CVE-2025-45846?

CVE-2025-45846 is a high-severity memory corruption vulnerability in n/a, published on 8 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ALFA AIP-W512 v3.2.2.2.3 was discovered to contain an authenticated stack overflow via the torrentsindex parameter in the formBTClinetSetting function.

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

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

It affects 1 product.


Products: Alfa Aip-W512 Firmware.

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

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

## Is CVE-2025-45846 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-45847](https://insights.sbomify.com/CVE-2025-45847/): Memory corruption in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-45846 is a high-severity memory corruption vulnerability in n/a, published on 8 May 2025. 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-2025-45846 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-45846/ (Markdown: https://insights.sbomify.com/CVE-2025-45846/index.md)
```

## Sources

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

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