VulertSecurity VulertSecurity

Vulnerability Database · OSS-Fuzz · Package report

gstreamer: vulnerability history, versions and safety

gstreamer is a package in the OSS-Fuzz ecosystem. Vulert records 6 vulnerabilities for it across 51 releases, from Jan 2021 to Sep 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
6 vulnerabilities recorded H2 M4
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all gstreamer vulnerabilities

Vulert verdict on gstreamer i

Updated on 23 Oct 2026

Careful: one of the 6 vulnerabilities Vulert records for this package has no fix yet. Plan around that one, or apply its workaround. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 6 vulnerabilities on record across 2 years, none in the last year.

What to do: Plan around the 1 vulnerability with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 6 over 2 years · 0 in the last year i
  • Latest disclosure 16 Sep 2023 i
  • Highest CVSS n/a i
  • With no published fix 1 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for gstreamer, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 51 of 51 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 3
  • 2022 2
  • 2023 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 6 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for gstreamer

The 5 most severe of 6 vulnerabilities recorded for this package

Search all 6 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Heap-buffer-overflow in pnm_type_find in gstreamer N/A medium d106390adce5cee837d2d0aab377d758a45a4b2d 13 Jan 2021
UNKNOWN READ Vulnerability in gstreamer N/A medium b71841c2d2f3759abc5ebe2703cc96c18da77dc9 13 Jan 2021
Heap-buffer-overflow in tap_type_find in gstreamer N/A medium 80dfb7bb3f415dac465f89f8945a1546c4fcc280 13 Jan 2021
Heap-buffer-overflow in parse_subrip in gstreamer N/A medium 0405e0cfc7974cd9369747077fb388144e8bc4de 25 Oct 2022
Heap-buffer-overflow in parse_subrip in gstreamer N/A high No fix published 12 Nov 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About gstreamer

Is gstreamer safe to use?

Vulert records 6 vulnerabilities for gstreamer in OSS-Fuzz: 0 critical, 2 high, 4 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

How many vulnerabilities does gstreamer have?

6 vulnerabilities are recorded for gstreamer in the OSS-Fuzz ecosystem: 0 critical, 2 high, 4 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new gstreamer vulnerabilities disclosed?

0 vulnerabilities were recorded for gstreamer in the last 12 months, and the oldest entry in this database dates to 13 Jan 2021. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of gstreamer are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor gstreamer for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the gstreamer version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.