dbcve.org
CWE-259Weakness · CWE-259

CVE-2026-35905

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

T3 Technology CPE models (T625Pro, T6825G, T7281) contain a hardcoded password embedded in firmware that provides root access via a 'superadmin' account, creating a critical backdoor that allows unauthenticated attackers to gain full administrative control over affected devices.

MitigationContact vendor for firmware updates addressing the hardcoded credentials; if unavailable, replace affected devices. Implement network segmentation and restrict external access to CPE management interfaces as an interim control.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Check the CPE device label, web UI footer, or CLI output for model number (T625Pro, T6825G, or T7281)
    Affected if Device is one of these three T3 Technology models
  2. Locate device management interface
    Access the web-based admin panel (typically on ports 80/443) or check for open SSH/Telnet on the device
    Affected if Management interface is accessible (device is on your network)
  3. Check firmware version
    Log into the web UI and look for a 'System Info' or 'Firmware Version' page, or run 'cat /proc/version' or 'uname -a' via serial/SSH if available
    Affected if Firmware version cannot be verified as patched (no patch information available for this CVE)
  4. Test for hardcoded superadmin access
    Attempt to log into the web UI or CLI using the superadmin account with the hardcoded backup password (the password is documented in public CVE sources)
    Affected if Authentication succeeds without valid user credentials - confirms the hardcoded credential is present and exploitable

You are affected if you have a T625Pro, T6825G, or T7281 device with its management interface exposed, and the superadmin account accepts the hardcoded password for pre-authentication root access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Contact vendor for firmware updates addressing the hardcoded credentials; if unavailable, replace affected devices. Implement network segmentation and restrict external access to CPE management interfaces as an interim control.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-35905 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-35905 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data