# CVE-2026-1453: Missing Authentication for Critical Function in KiloView Encoder Series

> Unauthenticated attackers can create or delete administrator accounts on KiloView encoders, gaining full administrative control.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/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:** 29 Jan 2026
- **Updated:** 29 Jan 2026
- **Also known as:** GHSA-x5qw-m467-vgq3

## What is CVE-2026-1453?

CVE-2026-1453 is a critical missing authorization vulnerability in KiloView Encoder Series E1 hardware Version 1.4, published on 29 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A missing authentication for critical function vulnerability in KiloView Encoder Series could allow an unauthenticated attacker to create or delete administrator accounts. This vulnerability can grant the attacker full administrative control over the product.

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

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


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

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

## Is CVE-2026-1453 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-1453 is a critical missing authorization vulnerability in KiloView Encoder Series E1 hardware Version 1.4, published on 29 Jan 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-1453 in the wild and no public exploit code.

Affected product: KiloView Encoder Series E1 hardware Version 1.4. 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-1453/ (Markdown: https://insights.sbomify.com/CVE-2026-1453/index.md)
```

## Sources

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

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