# CVE-2026-111100: Kiloview E3 NDI Encoder Missing Authentication for Critical Function


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-xg55-fcfc-cqx9

## What is CVE-2026-111100?

CVE-2026-111100 is a medium-severity vulnerability in Kiloview E3 Firmware, published on 22 Oct 2026. 

### Official description

The ONVIF device service on the E3 responds to certain informational requests without requiring authentication. A remote, unauthenticated party can retrieve detailed device identifiers along with a list of configured user accounts and their privilege levels. This aids attackers in fingerprinting vulnerable devices and preparing targeted credential attacks.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-111100 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111100 is a medium-severity vulnerability in Kiloview E3 Firmware, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-111100 in the wild and no public exploit code.

Affected product: Kiloview E3 Firmware. 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-111100/ (Markdown: https://insights.sbomify.com/CVE-2026-111100/index.md)
```

## Sources

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

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