dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-7766

HIGH · 8.3 CVSS v4.0 Published 2026-05-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
88/100
Remediation priority · High
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
Kenik Camera management Panel is vulnerable to Path Traversal vulnerability. An unauthenticated attacker can send GET request with arbitrary file path and read corresponding files located on the server. The issue was fixed in version 2026-04-23 of the KG-5260xxxx-IL-(G)2 cameras. Rest of the products were fixed in version 2025-04-21.

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 · high confidence

Kenik Camera management Panel suffers from a Path Traversal vulnerability (CWE-22) that allows unauthenticated attackers to craft GET requests containing directory traversal sequences (e.g., ../../) to access files outside the web root. The vulnerability stems from insufficient input validation on file path parameters, enabling arbitrary file disclosure across the filesystem.

MitigationApply the vendor-supplied firmware updates (version 2026-04-23 for KG-5260xxxx-IL-(G)2 cameras, 2025-04-21 for other products) to all affected camera devices and restrict external network access to the camera management interface.

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
Adjacent
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 Kenik Camera management Panel is exposed
    Scan your network for the Kenik Camera management Panel web interface. Look for HTTP/HTTPS services on ports typically used by camera management (80, 443, 8080, 8443). Check for login pages or panels referencing 'Kenik' or camera management.
    Affected if The panel is accessible over the network without authentication restrictions.
  2. Determine the firmware version
    Access the camera web interface and navigate to System, Settings, or About page to find the firmware version. Alternatively, check the HTTP response headers or the login page source for version strings.
    Affected if The firmware version is earlier than 2026-04-23 for KG-5260xxxx-IL-(G)2 models, or earlier than 2025-04-21 for other affected models.
  3. Verify unauthenticated access is possible
    Attempt to access the camera management interface without providing credentials. Check if the main panel or certain features are accessible without a login prompt.
    Affected if The management panel or sensitive endpoints are reachable without authentication.
  4. Test for path traversal vulnerability
    Send a crafted GET request to the panel with a path traversal payload such as '../' or '..\' in the URL parameters. For example: http://[target]/api/readfile?file=../../etc/passwd or similar endpoints that accept file paths. Check if the response contains file contents.
    Affected if The server returns file contents from outside the web root directory without requiring authentication.

You are affected if the Kenik Camera management Panel is accessible and its firmware version is below the fixed releases (2026-04-23 or 2025-04-21 depending on model), or if the path traversal endpoint returns sensitive files without authentication.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied firmware updates (version 2026-04-23 for KG-5260xxxx-IL-(G)2 cameras, 2025-04-21 for other products) to all affected camera devices and restrict external network access to the camera management interface.

Recommended fix Moderate confidence

2026-04-23 for KG-5260xxxx-IL-(G)2 cameras; 2025-04-21 for other products

  1. Identify the Kenik camera model in your environment (e.g., KG-5260xxxx-IL-(G)2 or other models)
  2. Check the current firmware version of each camera
  3. For KG-5260xxxx-IL-(G)2 cameras: upgrade to firmware version 2026-04-23 or later
  4. For all other Kenik camera models: upgrade to firmware version 2025-04-21 or later
  5. After upgrade, verify the path traversal vulnerability is no longer exploitable by attempting to access a test file outside the web root

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-7766 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