Severity:

HIGH RISK

(7.3)

Path Traversal in Tenda i9 HTTP

CVE-2026-7036

Analyzed

Vulnerability type

Category:

Path Traversal

CWE:

CWE-22

Impact:

Unauthorized File System Access

Severity:

HIGH RISK

(7.3)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A path traversal vulnerability in the Tenda i9 router's HTTP handler (R7WebsSecurityHandlerfunction) allows crafted requests to manipulate file paths processed by the web service.

Under certain conditions, a remote attacker can access files or directories outside the intended web root, potentially exposing sensitive information or influencing device behavior.

Affected context

This issue occurs in the Tenda i9 firmware version 1.0.0.5(2204) within the HTTP handling logic of R7WebsSecurityHandlerfunction.

It manifests when user-controlled input is incorporated into file system paths used by the router's web interface without adequate normalization or restriction.

The vulnerability is relevant where the device's management interface is reachable over the network and where underlying file system paths map to security-relevant configuration or data.

Exploit preconditions

  • Attack surface: HTTP interface of the Tenda i9 router (web management endpoint)
  • Required access: Network-level access to the router's HTTP service (e.g., LAN, Wi-Fi, or exposed WAN if misconfigured)
  • Trigger point: Submission of crafted HTTP requests that manipulate path parameters consumed by R7WebsSecurityHandlerfunction
  • Why exploitation is possible: The handler incorporates untrusted path segments into file operations without enforcing a strict base directory, canonicalization, or validation to prevent traversal sequences (such as parent directory references).

Why this happens

The root cause aligns with CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal').

The HTTP handler accepts user-supplied data that influences file paths and fails to constrain these paths to a safe, predefined directory.

Without proper checks (such as normalization, disallowing directory traversal tokens, and enforcing a fixed root), the code can resolve to unintended locations on the file system, exposing files or configuration elements that should remain inaccessible via the web interface.

Potential impact

  • May allow attackers to read files outside the intended web root that are accessible to the HTTP process
  • Could expose sensitive configuration data, credentials, or logs that aid in further compromise
  • Can enable information gathering about the device's file system layout and internal structure
  • Might assist in chaining with other vulnerabilities (e.g., file inclusion or configuration manipulation) for deeper control over the device

General mitigation guidance

Effective mitigation generally focuses on rigorous path handling and isolation:

  • Constrain all web-accessible file operations to a fixed, validated base directory and reject any paths that escape this root after canonicalization.
  • Normalize and sanitize incoming path parameters, removing or rejecting traversal sequences and other unsafe constructs instead of merely filtering string patterns.
  • Use high-level file access wrappers that enforce directory whitelists rather than constructing file paths manually from request parameters.
  • Reduce the privileges of the web service process so that, even if traversal occurs, the accessible file set is minimized.
  • Segment administrative interfaces from untrusted networks and restrict access to authenticated, authorized administrators where possible.

How teams detect issues like this

Organizations and developers can detect this class of issue through:

  • Static analysis rules that flag uses of user-controlled input in file system operations without canonicalization and base-directory enforcement.
  • Manual code review focused on HTTP handlers and routing logic that construct paths from query parameters, URL segments, or form data.
  • Security testing and fuzzing of the web interface, specifically probing for directory traversal patterns and validating that responses do not leak unintended files.
  • Configuration and policy checks that ensure management interfaces are not unnecessarily exposed to the public internet, reducing exploitability.

Sources

SourceLink
github.comgithub.com/Litengzheng/vuldb_new/blob/main/M3/vul_80/README.md
vuldb.comvuldb.com/submit/798479
vuldb.comvuldb.com/vuln/359616
vuldb.comvuldb.com/vuln/359616/cti
tenda.com.cntenda.com.cn/

Frequently asked

questions

Yes. An attacker with network access to the router's HTTP interface can attempt to exploit the vulnerability remotely, without requiring local device access.

The attacker must be able to send HTTP requests to the Tenda i9 management interface. This is often limited to the local network by default but can be reachable from external networks if remote management is enabled or misconfigured.

Enforce strict path constraints by resolving requested paths against a fixed base directory after canonicalization, rejecting any request that attempts to leave that directory, and avoid directly concatenating user input into file paths.

Apply defensive coding patterns for all file operations involving user input, incorporate static analysis and code review checks targeting path manipulation, and design web handlers to operate on logical resource identifiers rather than raw file system paths whenever possible.

Find out what's already
exploitable in your codebase.