# CVE-2026-82487: Beetel 450TC3 password recovery

> Remote attackers can exploit weak password recovery mechanisms to gain unauthorized access to Beetel 450TC3 devices.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **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 Aug 2026
- **Updated:** 1 Sep 2026
- **Also known as:** GHSA-42p8-vfg5-26vr

## What is CVE-2026-82487?

CVE-2026-82487 is a medium-severity vulnerability in Beetel 450TC3, published on 30 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was determined in Beetel 450TC3 01.00.00_01. This affects an unknown part. Executing a manipulation can lead to weak password recovery. The attack can be executed remotely. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-640 (Weak Password Recovery Mechanism for Forgotten Password)

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


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

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

## Is CVE-2026-82487 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82487 is a medium-severity vulnerability in Beetel 450TC3, published on 30 Aug 2026. 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-2026-82487 exists.

Affected product: Beetel 450TC3. 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-82487/ (Markdown: https://insights.sbomify.com/CVE-2026-82487/index.md)
```

## Sources

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

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