# CVE-2025-12917: TOZED ZLT T10 Reboot proc_post denial of service

> A denial of service vulnerability in the TOZED ZLT T10 Reboot Handler allows local network attackers to disrupt service via the proc_post endpoint.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Nov 2025
- **Updated:** 13 Nov 2025
- **Also known as:** GHSA-vvg5-qhqr-r6vw

## What is CVE-2025-12917?

CVE-2025-12917 is a medium-severity denial of service vulnerability in TOZED ZLT T10, published on 9 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was identified in TOZED ZLT T10 T10PLUS_3.04.15. The affected element is an unknown function of the file /reqproc/proc_post of the component Reboot Handler. Such manipulation leads to denial of service. Access to the local network is required for this attack to succeed. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-404 (Improper Resource Shutdown or Release)

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

It affects 1 product.


Products: Gztozed Zlt T10 Plus Firmware.

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

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

## Is CVE-2025-12917 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-12917 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-12917 is a medium-severity denial of service vulnerability in TOZED ZLT T10, published on 9 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-12917 exists.

Affected product: TOZED ZLT T10. 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-12917/ (Markdown: https://insights.sbomify.com/CVE-2025-12917/index.md)
```

## Sources

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

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