CVE-2026-1940: Red Hat Enterprise Linux 10 · Out-of-bounds Read
Affects Red Hat Enterprise Linux 10Source CVE Database V5
Mentioned vulnerabilities
Not known to be exploited · CVSS 5.1 Medium.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 23 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat Enterprise Linux 10gstreamer1 | Affected– | Fixed in– |
| Red Hat Enterprise Linux 6gstreamer | Affected– | Fixed in– |
| Red Hat Enterprise Linux 7gstreamer | Affected– | Fixed in– |
| Red Hat Enterprise Linux 7gstreamer1 | Affected– | Fixed in– |
| Red Hat Enterprise Linux 8gstreamer1 | Affected– | Fixed in– |
| Red Hat Enterprise Linux 8mingw-gstreamer1 | Affected– | Fixed in– |
AI-suggested
To mitigate CVE-2026-1940, organizations should: 1) Apply official patches from Red Hat as soon as they become available to ensure the incomplete fix is corrected. 2) Audit and restrict local user access to systems running Red Hat Enterprise Linux 10, especially those processing untrusted or user-supplied WAV files. 3) Implement strict input validation and sanitization for multimedia files before processing to reduce the risk of triggering the vulnerability. 4) Monitor system logs and application behavior for crashes or anomalies related to GStreamer or WAV file parsing. 5) Consider deploying application-level sandboxing or containerization for multimedia processing services to limit the impact of potential exploitation. 6) Keep GStreamer and related multimedia libraries up to date and review any custom patches or third-party plugins that might interact with WAV parsing. 7) Educate system administrators and developers about the importance of accounting for alignment and rounding in buffer size calculations to prevent similar issues.
Description
An incomplete fix for CVE-2024-47778 allows an out-of-bounds read in gst_wavparse_adtl_chunk() function. The patch added a size validation check lsize + 8 > size, but it does not account for the GST_ROUND_UP_2(lsize) used in the actual offset calculation. When lsize is an odd number, the parser advances more bytes than validated, causing OOB read.
References
- access.redhat.com/security/cve/CVE-2026-1940 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2436932 (opens in a new tab)
- gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/4854 (opens in a new tab)
- gstreamer.freedesktop.org/security/sa-2026-0001.html (opens in a new tab)
- security-tracker.debian.org/tracker/CVE-2026-1940 (opens in a new tab)