# CVE-2026-120458: Kvazaar through 2.3.2 Infinite Loop DoS via Y4M Header Parser


- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 2 Nov 2026
- **Updated:** 7 Nov 2026
- **Also known as:** GHSA-chw9-qpvj-3r3m, UBUNTU-CVE-2026-120458

## What is CVE-2026-120458?

CVE-2026-120458 is a medium-severity vulnerability in Ultra Video Group Kvazaar, published on 2 Nov 2026. 

### Official description

Kvazaar through 2.3.2 contains an infinite loop vulnerability in read_header() in src/encmain.c that allows attackers to hang the command-line encoder by supplying a truncated Y4M header. Attackers can provide a crafted .y4m file lacking a terminating newline, causing unchecked EOF reads that hang the process indefinitely while consuming a full CPU core.

Weakness: CWE-835 (Loop with Unreachable Exit Condition)

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


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

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

## Is CVE-2026-120458 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120458 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120458 is a medium-severity vulnerability in Ultra Video Group Kvazaar, published on 2 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120458 exists.

Affected product: Ultra Video Group Kvazaar. 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-120458/ (Markdown: https://insights.sbomify.com/CVE-2026-120458/index.md)
```

## Sources

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

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