# CVE-2026-35904: Missing authorization in n/a

> Unauthorized attackers can enable Telnet on T3 Technology CPE devices via a crafted request, potentially leading to remote code execution.

- **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:** 4 Jun 2026
- **Updated:** 8 Jun 2026
- **Also known as:** GHSA-2cm6-668w-rvw2

## What is CVE-2026-35904?

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

### Official description

Incorrect access control in the web management interface of T3 Technology CPE models T625Pro v1.0.07, T6825G v1.0.03, and T7281 v1.0.03 allows unauthorized attackers to enable the Telnet service via sending a crafted request to a vulnerable CGI component.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-35904 being exploited?

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

Public exploit code:

- CVE-2026-35904 / CVE-2026-35905 / CVE-2026-35906 — Unauth RCE, Hardcoded Root Creds & Telnet Enable in T3 Technology CPE (github_poc): https://github.com/PwnOnu/T3-Technology-CPE-Advisories

## Fix prompt for AI coding agents

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

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

## Sources

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

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