# CVE-2026-7739: justdan96 tsMuxer hevc.cpp setFPS denial of service

> Local attackers can cause a denial of service in tsMuxer via the setFPS function, affecting unsupported versions.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 May 2026
- **Updated:** 4 May 2026
- **Also known as:** GHSA-x2qh-qj48-7p3r

## What is CVE-2026-7739?

CVE-2026-7739 is a medium-severity denial of service vulnerability in justdan96 tsMuxer, published on 4 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A weakness has been identified in justdan96 tsMuxer up to 2.7.0. This vulnerability affects the function HevcVpsUnit::setFPS of the file /AFLplusplus/tsMuxer_prev/tsMuxer/hevc.cpp. This manipulation of the argument track_id causes denial of service. The attack requires local access. The exploit has been made available to the public and could be used for attacks. This vulnerability only affects products that are no longer supported by the maintainer.

Weakness: CWE-404 (Improper Resource Shutdown or Release)

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


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

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

## Is CVE-2026-7739 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7739 is a medium-severity denial of service vulnerability in justdan96 tsMuxer, published on 4 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7739 exists.

Affected product: justdan96 tsMuxer. 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-7739/ (Markdown: https://insights.sbomify.com/CVE-2026-7739/index.md)
```

## Sources

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

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