VYPR
Critical severity9.6NVD Advisory· Published Jun 4, 2026· Updated Jun 4, 2026

CVE-2026-35906

CVE-2026-35906

Description

An undocumented debug CGI endpoint in T3 Technology CPE models allows unauthenticated attackers to execute arbitrary system commands as root via crafted HTTP queries.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

An undocumented debug CGI endpoint in T3 Technology CPE models allows unauthenticated attackers to execute arbitrary system commands as root via crafted HTTP queries.

Vulnerability

An undocumented debug CGI endpoint, /cgi-bin/shortcut_telnet.cgi, exists in T3 Technology CPE models T625Pro v1.0.07 and T6825G v1.0.03. This endpoint is susceptible to OS command injection and does not require any authentication to be reached [1].

Exploitation

An attacker can exploit this vulnerability by sending a crafted HTTP query string to the debug endpoint. While the endpoint is only reachable from the LAN, the vulnerability is exploitable via Blind CSRF. An external attacker can host a malicious page that, when visited by a user on the target network, triggers command execution on the CPE device without the attacker needing direct LAN access [1].

Impact

Successful exploitation allows an attacker to execute arbitrary operating system commands with root privileges on the affected device. This can lead to a complete compromise of the device's confidentiality, integrity, and availability [1].

Mitigation

No patched version or specific mitigation details are available in the provided references. The T625Pro v1.0.07 and T6825G v1.0.03 are confirmed or suspected to be affected. It is unknown if other T3 Technology models or firmware versions are vulnerable [1].

AI Insight generated on Jun 4, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

4

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

4

News mentions

0

No linked articles in our index yet.