# CVE-2021-46010: Auth bypass in n/a

> Predictable session IDs in Totolink routers allow attackers to hijack valid sessions and perform unauthorized actions.

- **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:** 30 Mar 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-4q2f-j497-jmqf

## What is CVE-2021-46010?

CVE-2021-46010 is a high-severity authentication bypass vulnerability in n/a, published on 30 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Totolink A3100R V5.9c.4577 suffers from Use of Insufficiently Random Values via the web configuration. The SESSION_ID is predictable. An attacker can hijack a valid session and conduct further malicious operations.

Weakness: CWE-330 (Use of Insufficiently Random Values)

## Which versions are affected by CVE-2021-46010?

It affects 1 product.


Products: Totolink A3100r Firmware.

## How do I fix CVE-2021-46010?

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

## Is CVE-2021-46010 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-28256](https://insights.sbomify.com/CVE-2025-28256/): Command injection in n/a (critical 9.8)
- [CVE-2024-42546](https://insights.sbomify.com/CVE-2024-42546/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-42547](https://insights.sbomify.com/CVE-2024-42547/): Memory corruption in n/a (critical 9.8)
- [CVE-2022-29644](https://insights.sbomify.com/CVE-2022-29644/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2022-29645](https://insights.sbomify.com/CVE-2022-29645/): Hardcoded credentials in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-46010 and fix it if it is affected.

What it is: CVE-2021-46010 is a high-severity authentication bypass vulnerability in n/a, published on 30 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-46010 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-2021-46010/ (Markdown: https://insights.sbomify.com/CVE-2021-46010/index.md)
```

## Sources

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

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