dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-35906

CRITICAL · 9.6 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

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
An undocumented debug CGI endpoint in T3 Technology CPE models T625Pro v1.0.07, T6825G v1.0.03 allows unauthenticated attackers to execute arbitrary system commands as root via supplying a crafted HTTP query string.

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

An undocumented debug CGI endpoint in T3 Technology CPE models T625Pro v1.0.07 and T6825G v1.0.03 permits unauthenticated remote attackers to execute arbitrary system commands with root privileges by submitting a crafted HTTP query string to the endpoint.

MitigationRestrict network access to affected devices, implement firewall rules to block external access to debug endpoints, and monitor for signs of exploitation until a vendor firmware patch is available.

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
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 interface header, or SNMP sysDescr for 'T625Pro' or 'T6825G' model identifier
    Affected if Device is a T3 Technology T625Pro or T6825G model
  2. Check firmware version
    Access the device web interface (typically at http://<device-ip>/) and locate the firmware version in the system settings or status page, or check via CLI 'cat /etc/version' if SSH/telnet access is available
    Affected if Firmware version is v1.0.07 for T625Pro or v1.0.03 for T6825G (or lower unpatched versions)
  3. Locate undocumented debug CGI endpoint
    Search the device firmware filesystem (via firmware extraction or debug access) for CGI files not documented in the user manual, or check the web server configuration for hidden debug scripts
    Affected if An undocumented debug CGI endpoint exists on the device
  4. Verify network exposure
    Check router/firewall rules to determine if the device web management interface (port 80/443) is accessible from external networks or the internet rather than only from a trusted LAN
    Affected if The device web interface is exposed to untrusted networks or the internet without authentication barriers

You are affected if your T3 Technology CPE device runs unpatched firmware (T625Pro v1.0.07 or lower, T6825G v1.0.03 or lower) AND the undocumented debug CGI endpoint is present AND the device is network-accessible to potential attackers.

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

Restrict network access to affected devices, implement firewall rules to block external access to debug endpoints, and monitor for signs of exploitation until a vendor firmware patch is available.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-35906 — 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-35906 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