CVE-2026-110654 zapping-vbi CVE debrief

Who should care

Defenders of Teletext stream processing environments using libzvbi should assess exposure and prioritize verification of vulnerable libzvbi versions. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify vulnerable libzvbi versions and assess exposure in their environments.

Why it matters

Defenders of Teletext stream processing environments using libzvbi should assess exposure and prioritize verification of vulnerable libzvbi versions due to potential memory corruption and application crash.

• Potential memory corruption and application crash
• Verification of vulnerable libzvbi versions is required
• Remediation priority for libzvbi versions in Teletext stream processing environments

Technical summary

libzvbi through 0.2.45 contains an out-of-bounds write vulnerability in the Teletext decoder that allows attackers to corrupt memory by supplying unvalidated DRCS pixel-mode values in X/28/3 packets. Attackers can send a crafted Teletext stream decoded via vbi_decode with every slot set to DRCS_MODE_6_5_4, causing convert_drcs to overflow chars[48][60] and crash the application. Defenders of Teletext stream processing environments using libzvbi should assess exposure and prioritize verification of vulnerable libzvbi versions.

Defensive priority

Assess exposure and prioritize verification of vulnerable libzvbi versions in Teletext stream processing environments.

Recommended defensive actions

• Assess exposure of libzvbi versions in Teletext stream processing environments
• Prioritize verification of vulnerable libzvbi versions
• Verify vendor remediation for libzvbi
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the out-of-bounds write vulnerability in libzvbi through 0.2.45. The vulnerability allows attackers to corrupt memory by supplying unvalidated DRCS pixel-mode values in X/28/3 packets. Defenders should verify vulnerable libzvbi versions and assess exposure in Teletext stream processing environments. The source item provides details on the out-of-bounds write vulnerability in libzvbi through 0.2.45.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.