CVE-2024-47775VulnerabilityPublished 8 May 2026Updated 10 Sep 2026

CVE-2024-47775: GHSL-2024-261 · GStreamer has an OOB-read in parse_ds64

Affects jreSource GCVE Database

Not known to be exploited : upgrade to 8.0.451 or 1.8.0 as a priority.

Data as of 25 Oct 2026, 19:02 UTC

Severity

Critical

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 1.1% chance of exploitation in 30 days – higher than 67% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 8.0.451, 1.8.0

Exploitation evidence

Disclosed: evidence found.
CVE published 8 May 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 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade jre to 8.0.451 or 1.8.0.

Patches and advisories

gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/8042.patch (opens in a new tab)

Affected software

Product	Affected	Fixed in
Bitnamijre`pkg:bitnami/jre`Other threats	Affected <1.8.0 >=1.9.0 <8.0.451	Fixed in 1.8.0 8.0.451

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in GStreamer version 1.24.10. Users should upgrade to this version or later to remediate the vulnerability.

Description

An out-of-bounds read vulnerability exists in the parse_ds64 function of GStreamer's gstwavparse.c. The function fails to verify buffer length before reading, which can cause reading beyond the buffer boundary. This may lead to application crashes or sensitive data leakage. The issue is fixed in version 1.24.10.

Impact

Exploitation of this vulnerability can result in application crashes (denial of service) or unintended disclosure of sensitive data due to out-of-bounds memory reads.

Summary

GStreamer, a media-handling library, contains an out-of-bounds read vulnerability (CVE-2024-47775) in the parse_ds64 function within gstwavparse.c. The function performs multiple GST_READ_UINT32_LE operations without checking that the input buffer is sufficiently large, allowing reads beyond the buffer's end if it is smaller than expected. This can cause denial of service via crashes or potentially leak sensitive information. The vulnerability is addressed in GStreamer version 1.24.10.

References

Community reviews

Loading reviews…