T3 T625Pro/T7281 hard-coded password

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.9$0-$5k0.00

Summaryinfo

A vulnerability was found in T3 T625Pro and T7281. It has been classified as critical. This affects an unknown part. This manipulation causes hard-coded password. The identification of this vulnerability is CVE-2026-35905. There is no exploit available.

Detailsinfo

A vulnerability was found in T3 T625Pro and T7281 (unknown version). It has been declared as critical. Affected by this vulnerability is an unknown code block. The manipulation with an unknown input leads to a hard-coded password vulnerability. The CWE definition for the vulnerability is CWE-259. The product contains a hard-coded password, which it uses for its own inbound authentication or for outbound communication to external components. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

T3 Technology CPE models T625Pro v1.0.07, T6825G v1.0.03, and T7281 v1.0.03 were discovered to contain a hardcoded password for root access under the "superadmin" account.

This vulnerability is known as CVE-2026-35905 since 04/06/2026. The exploitation appears to be difficult. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 06/04/2026). The attack technique deployed by this issue is T1078.001 according to MITRE ATT&CK.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Vendor

Name

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.1
VulDB Meta Temp Score: 6.9

VulDB Base Score: 7.1
VulDB Temp Score: 6.9
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Hard-coded password
CWE: CWE-259 / CWE-255
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔒

Timelineinfo

04/06/2026 CVE reserved
06/04/2026 +59 days Advisory disclosed
06/04/2026 +0 days VulDB entry created
06/04/2026 +0 days VulDB entry last update

Sourcesinfo

Status: Not defined

CVE: CVE-2026-35905 (🔒)
GCVE (CVE): GCVE-0-2026-35905
GCVE (VulDB): GCVE-100-368359

Entryinfo

Created: 06/04/2026 17:27
Changes: 06/04/2026 17:27 (49)
Complete: 🔍
Cache ID: 216::103

Be aware that VulDB is the high quality source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!