Skip to main content

libaribb24 EUVDEUVD-2026-104292

| CVE-2026-112281 MEDIUM
Stack-based Buffer Overflow (CWE-121)
2026-10-19 disclosure@vulncheck.com GHSA-6rxg-9w2c-f7x4
6.9
CVSS 4.0 · Vendor: vulncheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Craft media file with oversized CSI parameters
  2. Delivery
    Deliver file or stream to victim
  3. Exploit
    Victim opens it in FFmpeg/VLC
  4. Execution
    Overflow fixed 256-entry stack array in decoder_handle_csi()
  5. Impact
    Crash process or corrupt return address

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Stack buffer bounds checking
MITRE ATT&CK

1 technique across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires an application (FFmpeg or VLC) compiled with aribb24 support that actually decodes ARIB STD-B24 caption data, and that caption data must contain a CSI introducer followed by more than 256 parameter bytes to overflow the fixed 256-entry array in decoder_handle_csi(). Limiting factors: the attack vector is local (AV:L) and requires passive user interaction (UI:P) - a victim must open or process the malicious media file or tune the crafted broadcast stream; it is not remotely triggerable without that content-processing step, and exposure is confined to deployments that enable the ARIB caption decoding path (predominantly Japanese broadcast content workflows).

Impact

This is a medium-severity, local-vector memory corruption issue, not a drop-everything emergency. The input CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:N/UI:P, score 6.9) indicates exploitation requires a local attack vector plus passive user interaction - i.e., a victim must open or process attacker-supplied content - rather than remote, unauthenticated triggering. No EPSS score, no CISA KEV listing, and no explicitly flagged POC were provided in the input, so there is no signal of active or probable widespread exploitation; this is 'no public exploit identified at time of analysis' per available data, though a detailed public technical write-up (hackmd) exists that documents the OOB-write mechanics and would lower the bar for exploit development. The impact signals conflict in a telling way: VA:H (availability) reflects the confirmed crash of FFmpeg/VLC, while VI:L (low integrity) and the description's 'corrupt the return address' language hint at possible control-flow hijack / RCE that is NOT established as reliably achievable - so treat code execution as plausible-but-unproven and the realistic impact as denial of service. Net: a real but bounded issue, prioritized where media/broadcast caption processing with aribb24 is actually in use, not a broad internet-facing priority.

Exploit ScenarioDerived

An attacker crafts a media file or broadcast stream embedding an ARIB caption statement with a CSI (Control Sequence Introducer) followed by more than 256 parameter bytes, then induces a victim to open it in FFmpeg or VLC built with aribb24 support. The decoder_handle_csi() routine writes past the fixed 256-entry stack array, crashing the application and potentially corrupting the saved return address. No public exploit code is identified in the provided data, though a detailed technical write-up of the overflow is publicly available.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 19, 2026

Stack-based buffer overflow in libaribb24 through 1.0.3 allows memory corruption when FFmpeg or VLC decodes ARIB STD-B24 caption data containing a CSI introducer followed by more than 256 parameter bytes. The assessed vector is local with passive user interaction, so exploitation requires a victim to open or process a crafted media file or broadcast stream in a deployment that enables ARIB caption decoding; impact includes crashes and limited integrity effects with high availability loss. No public exploit identified at time of analysis, making this a medium-severity issue rather than an emergency.

RemediationAI

No vendor-released patch identified at time of analysis; upgrade libaribb24 to a release later than 1.0.3 once a fixed version is published, and track the VulnCheck advisory at https://www.vulncheck.com/advisories/libaribb24-through-1.0.3-stack-buffer-overflow-via-decoder-handle-csi. Until then, disable ARIB STD-B24 caption decoding in FFmpeg/VLC builds, for example by building without aribb24 support or removing the relevant demuxer/decoder path; this prevents the vulnerable CSI handling but breaks ARIB caption playback. Avoid opening or tuning untrusted media or broadcast streams in deployments that require ARIB captions, and run FFmpeg/VLC with least privilege or in a sandbox to limit the impact of memory corruption. Filtering or truncating CSI sequences with more than 256 parameter bytes before the decoder may reduce exposure but can alter valid caption rendering and is not a complete fix.

Affected VersionsENISA

aribb24 0 ≤1.0.3

Affected Packages

euvd aribb24 no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

libaribb24 (aribb24) is a C library for decoding ARIB STD-B24 caption and character data used in Japanese broadcast workflows; FFmpeg and VLC can link it for caption rendering. In src/decoder.c, decoder_handle_csi() handles CSI control sequences and stores parameter bytes in a fixed 256-entry stack array without enforcing a bound, so a crafted sequence with more than 256 parameter bytes overflows the array (CWE-121). The vulnerable path is reached only when an application actually invokes ARIB caption decoding on attacker-influenced content; the supplied references point to the v1.0.3 source and a technical write-up, and no CPE strings were provided.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (vulncheck) PRIMARY 6.9 MEDIUM
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N
vuln.today AI 6.1 MEDIUM

Triggered by opening attacker-supplied media (AV:L, UI:R, PR:N); reliable crash gives A:H, possible return-address corruption gives I:L, no data disclosure so C:N.

3.1 AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H
4.0 AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (vulncheck).

CVSS VectorVendor: vulncheck

Attack Vector
Local
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
Passive
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
Low
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

libaribb24 (aribb24) through 1.0.3 contains a stack-based buffer overflow vulnerability in decoder_handle_csi() in src/decoder.c that allows attackers to write past a fixed 256-entry array by supplying unbounded CSI parameter bytes. Attackers can embed a caption statement with a CSI introducer and over 256 parameter bytes in media files or broadcast streams to crash FFmpeg or VLC or corrupt the return address.

Threat Intelligence Overview

EPSS Score
0.2%
Top 91% exploitable
Prevalence
Medium
niche ARIB caption library, but bundled with ubiquitous FFmpeg/VLC media frameworks
Social Media
1
Sightings
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation
Poc
System Exposure· derived
Small
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

34
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +34
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

A stack-based buffer overflow occurs when a program writes more data to a buffer located on the stack than it was allocated to hold.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy