CWE-288Weakness · CWE-288

CVE-2026-8598

CRITICAL · 9.1 CVSS v3.1 Published 2026-05-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

An undocumented configuration export port on ZKTeco CCTV cameras allows unauthenticated remote attackers to access sensitive information including open services and plaintext camera account credentials. This critical flaw stems from the port being left exposed without authentication requirements.

MitigationIsolate affected cameras behind firewalls or network segmentation to block unauthorized access to the undocumented port, and contact ZKTeco for firmware updates that address this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if the device is a ZKTeco CCTV camera
    Check the device's web interface, DHCP vendor information, or network discovery for ZKTeco-specific banners, MAC OUI lookup for ZKTeco (00:1B:2E or similar), or check for ZKTeco-specific HTTP headers/paths
    Affected if The device is confirmed to be a ZKTeco CCTV camera model
  2. Locate the undocumented configuration export port
    Perform a port scan against the camera's IP address looking for unusual or undocumented ports. Common ZKTeco management ports include 80, 443, 8080; the undocumented export port would be an additional port not listed in official documentation
    Affected if An undocumented or non-standard port is found listening on the camera, particularly one returning configuration or system data
  3. Test unauthenticated access to configuration export
    Send an HTTP request to the undocumented port (e.g., curl http://camera-ip:port/config/export or similar paths) without providing any credentials to see if sensitive configuration data is returned
    Affected if The endpoint responds with system information, service listings, or plaintext camera credentials without requiring authentication
  4. Verify credential exposure in exported configuration
    Inspect any configuration data retrieved from the undocumented port for plaintext usernames and passwords, device keys, or authentication tokens
    Affected if The exported configuration contains plaintext camera account credentials or sensitive authentication material
  5. Check network exposure of the undocumented port
    Determine if the undocumented port is accessible from untrusted networks (WAN, guest networks, internet) by reviewing firewall rules, port forwarding configurations, or performing external connectivity tests
    Affected if The undocumented configuration export port is accessible from outside the trusted local network

If the device is a ZKTeco CCTV camera with an undocumented port accessible without authentication that exposes plaintext credentials, the environment is affected by CVE-2026-8598.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Isolate affected cameras behind firewalls or network segmentation to block unauthorized access to the undocumented port, and contact ZKTeco for firmware updates that address this vulnerability.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8598 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-8598 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data