# CVE-2025-70520: Missing authorization in n/a

> Unauthenticated attackers can access sensitive device resources and logs via the websocket handler due to missing authentication checks.

- **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:** 7 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-r46f-86rj-p44j

## What is CVE-2025-70520?

CVE-2025-70520 is a critical missing authorization vulnerability in n/a, published on 7 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The websocket handler of Fanvil x7a firmware version 2.6.0.1182 does not enforce proper authentication restrictions against sessionless users. The lack of restrictions grants anyone the ability to view any device resources such as operational logs or perform diagnostic requests.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2025-70520 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-70520 is a critical missing authorization vulnerability in n/a, published on 7 Oct 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-70520 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-70520/ (Markdown: https://insights.sbomify.com/CVE-2025-70520/index.md)
```

## Sources

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

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