# CVE-2026-124311: Fraunhofer HHI VVdeC through 3.2.1 NULL Pointer Dereference via InterPrediction::xPredInterBlk


- **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:** 7 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-8xcr-xgj2-cmf5

## What is CVE-2026-124311?

CVE-2026-124311 is a medium-severity vulnerability in fraunhoferhhi vvdec, published on 7 Nov 2026. 

### Official description

Fraunhofer HHI VVdeC through 3.2.1 contains a NULL pointer dereference vulnerability in InterPrediction::xPredInterBlk that allows attackers to crash the decoder by switching SPS to enable reference wrap-around. Attackers can supply a crafted VVC bitstream activating a new SPS with sps_ref_wraparound_enabled_flag set, causing reads from missing PIC_RECON_WRAP buffers and denial of service.

Weakness: CWE-476 (NULL Pointer Dereference)

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


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

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

## Is CVE-2026-124311 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-124311 is a medium-severity vulnerability in fraunhoferhhi vvdec, published on 7 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-124311 in the wild and no public exploit code.

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

## Sources

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

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