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

Published Nov 7, 2026

Updated

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 spsrefwraparoundenabledflag set, causing reads from missing PICRECONWRAP buffers and denial of service.

Event History

Nov 7, 2026

CVE Published

via MITRE·02:17 PM

Data Sourced

via MITRE·02:17 PM

DescriptionSeverityWeakness

Data Sourced

via NVD·03:17 PM

DescriptionSeverityWeakness

Frequently Asked Questions

Which deployments are realistically exposed?

Deployments that use VVdeC to decode VVC bitstreams supplied by an attacker are exposed to denial of service. The issue is triggered during decoding, so systems that do not process untrusted VVC input are not exposed through this attack path.

What does an attacker need to provide to trigger the crash?

An attacker needs to supply a crafted VVC bitstream that switches to a new SPS and enables sps_ref_wraparound_enabled_flag. This causes the decoder to read missing PIC_RECON_WRAP buffers and dereference a NULL pointer.

How can I determine whether my build is affected?

VVdeC versions through 3.2.1 are affected. The vulnerable code path is InterPrediction::xPredInterBlk, where reference wrap-around processing can access the missing reconstruction-wrap buffers.

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

Event History

Frequently Asked Questions

Which deployments are realistically exposed?

What does an attacker need to provide to trigger the crash?

How can I determine whether my build is affected?

Company

Resources

Contact

Frequently Asked Questions

Which deployments are realistically exposed?

What does an attacker need to provide to trigger the crash?

How can I determine whether my build is affected?