# CVE-2026-132753: MP4v2 through 2.1.0 NULL Pointer Dereference via MP4RtpHintTrack::GetPayload


- **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:** 18 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-f83v-9wxp-m4mv, UBUNTU-CVE-2026-132753

## What is CVE-2026-132753?

CVE-2026-132753 is a medium-severity vulnerability in TechSmith mp4v2, published on 18 Nov 2026. 

### Official description

MP4v2 through 2.1.0 contains a NULL pointer dereference vulnerability in MP4RtpHintTrack::GetPayload() in src/rtphint.cpp that passes an unchecked rtpmap value to strchr(). Attackers can supply a crafted MP4 file whose RTP hint track has a corrupted hinf atom to crash mp4info or applications calling MP4GetHintTrackRtpPayload().

Weakness: CWE-476 (NULL Pointer Dereference)

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

1 open source package ship an affected version, including techsmith/mp4v2.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `techsmith/mp4v2` | GitHub | `pkg:github/techsmith/mp4v2` | All versions to 2.1.0 | None |

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

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

## Is CVE-2026-132753 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-132753 is a medium-severity vulnerability in TechSmith mp4v2, published on 18 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-132753 exists.

Affected packages and fixed versions:
- techsmith/mp4v2 (GitHub): affected all versions up to 2.1.0; no fix listed

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-132753/ (Markdown: https://insights.sbomify.com/CVE-2026-132753/index.md)
```

## Sources

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

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