# CVE-2026-7766: Path Traversal in Kenik cameras

> Unauthenticated attackers can read arbitrary files on Kenik camera management panels via path traversal, exposing sensitive server data.

- **Severity:** High 8.3 (`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`)
- **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:** 25 May 2026
- **Updated:** 26 May 2026
- **Also known as:** GHSA-85gf-3m67-qq6h

## What is CVE-2026-7766?

CVE-2026-7766 is a high-severity path traversal vulnerability in Kenik KG-5230DAS-IL-G3, published on 25 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-7766 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7766 is a high-severity path traversal vulnerability in Kenik KG-5230DAS-IL-G3, published on 25 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-7766 in the wild and no public exploit code.

Affected product: Kenik KG-5230DAS-IL-G3. 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-7766/ (Markdown: https://insights.sbomify.com/CVE-2026-7766/index.md)
```

## Sources

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

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