# CVE-2026-108504: Unauthorized information retrieval vulnerability in ZTE Z80 Ultra product

> Attackers can read device-related information due to insufficient access control in the ZTE Z80 Ultra framework.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Oct 2026
- **Updated:** 11 Oct 2026
- **Also known as:** GHSA-pv9h-j29r-q9hq

## What is CVE-2026-108504?

CVE-2026-108504 is a medium-severity missing authorization vulnerability in ZTE Z80 Ultra, published on 10 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

ZTE Z80 Ultra has an unauthorized information disclosure vulnerability. The access control for methods within the framework is insufficient. An attacker can exploit this method to read device-related information.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2026-108504?


## How do I fix CVE-2026-108504?

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

## Is CVE-2026-108504 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-108504 and fix it if it is affected.

What it is: CVE-2026-108504 is a medium-severity missing authorization vulnerability in ZTE Z80 Ultra, published on 10 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-108504 in the wild and no public exploit code.

Affected product: ZTE Z80 Ultra. 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-2026-108504/ (Markdown: https://insights.sbomify.com/CVE-2026-108504/index.md)
```

## Sources

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

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