# CVE-2026-8598: Unauthenticated Export Service in ZKTeco CCTV Cameras

> An unauthenticated export service on ZKTeco CCTV cameras exposes critical configuration data and account credentials to remote attackers.

- **Severity:** Critical 9.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 May 2026
- **Updated:** 20 May 2026
- **Also known as:** GHSA-r827-rrrf-hq75

## What is CVE-2026-8598?

CVE-2026-8598 is a critical vulnerability in ZKTeco SSC335-GC2063-Face-0b77 Solution Camera, published on 20 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An undocumented configuration export port is accessible on some models 
of ZKTeco CCTV cameras. This port does not require authentication and 
exposes critical information about the camera such as open services and 
camera account credentials.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

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


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

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

## Is CVE-2026-8598 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-8598 is a critical vulnerability in ZKTeco SSC335-GC2063-Face-0b77 Solution Camera, published on 20 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-8598 in the wild and no public exploit code.

Affected product: ZKTeco SSC335-GC2063-Face-0b77 Solution Camera. 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-8598/ (Markdown: https://insights.sbomify.com/CVE-2026-8598/index.md)
```

## Sources

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

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