# CVE-2025-26710: Information disclosure in T5400

> Attackers can access sensitive information via unauthorized interfaces due to improper access control configuration in the ZTE T5400.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2025
- **Updated:** 16 Sep 2025
- **Also known as:** GHSA-jjm9-3gv3-8hp8

## What is CVE-2025-26710?

CVE-2025-26710 is a low-severity vulnerability in ZTE T5400, published on 16 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

There is an an information disclosure vulnerability in ZTE T5400. Due to improper configuration of the access control mechanism, attackers can obtain information through interfaces without authorization, causing the risk of information disclosure.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-26710?


## How do I fix CVE-2025-26710?

No fix has been published for CVE-2025-26710 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-26710 being exploited?

There is no known exploitation of CVE-2025-26710 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-26710 and fix it if it is affected.

What it is: CVE-2025-26710 is a low-severity vulnerability in ZTE T5400, published on 16 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-26710 in the wild and no public exploit code.

Affected product: ZTE T5400. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-26710/ (Markdown: https://insights.sbomify.com/CVE-2025-26710/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-26710
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-26710
- OSV: https://osv.dev/vulnerability/CVE-2025-26710

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-26710/
Summaries are generated and may contain mistakes; the official description above is the record.