CVE-2026-73433

Gstreamer1-plugins-good: gstreamer: unsigned integer underflow in avidemux fujifilm strd parsing leading to out-of-bounds read/write

MEDIUM
6.6
CVSS Score
Published: August 12, 2026 at 07:05 PM UTC
Updated: September 23, 2026 at 03:28 PM UTC
4 products affected across 3 vendorsEnterprise LinuxGStreamerGstreamer

Using Red Hat Enterprise Linux 10 by Red Hat?

Get instant alerts when new vulnerabilities affect Red Hat Enterprise Linux 10 - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6.6
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

A flaw was found in GStreamer gst-plugins-good (avidemux). When parsing FUJIFILM metadata in an AVI strd chunk, gst_avi_demux_parse_strd() decrements a remaining-length counter by fixed offsets (98 and 10 bytes) without verifying sufficient data remains. For crafted strd payloads of exactly 106 or 107 bytes, the counter underflows to a very large unsigned value, causing subsequent null-terminated string scanning to read far beyond the allocated heap buffer. Date-format normalization may also write beyond the buffer end. Confirmed impacts include heap out-of-bounds read, out-of-bounds write, heap information disclosure (adjacent data appearing in parsed metadata), and application crash/denial of service. The avidemux element is auto-plugged by playbin, decodebin, and gst-discoverer, so opening or previewing a crafted AVI is sufficient to trigger the issue. Fixed upstream in gst-plugins-good 1.28.6 (GStreamer-SA-2026-0072).

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≤ 1.28.6
Vendor states this is fixed in 0:1.10.4-4.el7_9.3 (unaffected)
Vendor states this is fixed in 0:1.16.1-4.el8_4.2 (unaffected)
Vendor states this is fixed in 0:1.16.1-4.el8_6.3 (unaffected)
Vendor states this is fixed in 0:1.16.1-5.el8_8.3 (unaffected)
Vendor states this is fixed in 0:1.16.1-7.el8_10.3 (unaffected)
Vendor states this is fixed in 0:1.18.4-8.el9_2.3 (unaffected)
Vendor states this is fixed in 0:1.22.1-4.el9_4.3 (unaffected)
Vendor states this is fixed in 0:1.22.12-5.el9_6.3 (unaffected)
Vendor states this is fixed in 0:1.22.12-7.el9_8.4 (unaffected)
Vendor states this is fixed in 0:1.24.11-1.el10_0.4 (unaffected)
Vendor states this is fixed in 0:1.26.7-2.el10_2.5 (unaffected)
v < 1.28.6
Affected range stops below 1.28.6, so it looks safe — our inference, not a vendor statement

References (15)

VDB Entryx_refsource_REDHATThird Party Advisory
Source: cverecord
https://access.redhat.com/security/cve/CVE-2026-73433
Issue Trackingx_refsource_REDHATThird Party Advisory
Source: cverecord
https://bugzilla.redhat.com/show_bug.cgi?id=2514801
Vendor Advisoryx_refsource_REDHATThird Party Advisory
Source: cverecord
https://access.redhat.com/errata/RHSA-2026:55434
Vendor Advisoryx_refsource_REDHATThird Party Advisory
Source: cverecord
https://access.redhat.com/errata/RHSA-2026:55436
Vendor Advisoryx_refsource_REDHAT
Source: cverecord
https://access.redhat.com/errata/RHSA-2026:56966
Vendor Advisoryx_refsource_REDHAT
Source: cverecord
https://access.redhat.com/errata/RHSA-2026:65959

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

6.6MEDIUMredhat
Attack Vector
LOCAL
Complexity
LOW
Privileges
NONE
User Interaction
REQUIRED
Scope
UNCHANGED
Confidentiality
LOW
Integrity
LOW
Availability
HIGH
Vector?

Quick Info

StatusUNDERGOING ANALYSIS
CWE
CWE-191

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card