VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

ccextractor: vulnerability history, versions and safety

ccextractor is a package in the Debian ecosystem. Vulert records 28 vulnerabilities for it across 7 releases, from Nov -0001 to Feb 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
28 vulnerabilities recorded U28
i
28 with no fix published

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

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

Most recent disclosure 21 Feb 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all ccextractor vulnerabilities

Vulert verdict on ccextractor i

Updated on 23 Oct 2026

Careful: 28 of the 28 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each.

Long-term outlook: usable, but needs attention 28 vulnerabilities on record across 2026 years, 1 in the last year.

What to do: Plan around the 28 vulnerabilities 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 28 over 2026 years · 1 in the last year i
  • Latest disclosure 21 Feb 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 28 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 ccextractor, 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.

i
Version Vulert vulnerabilities Fix published Details
0.94+ds1-3 U28 No Details →
0.94+ds1-2 U28 No Details →
0.94+ds1-1 U28 No Details →
0.93+ds2-2 U28 No Details →
0.93+ds2-1 U28 No Details →
0.93+ds1-1 U28 No Details →
0.88+ds1-1 U28 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 0 1
  • 2019 9
  • 2020 3
  • 2021 14
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for ccextractor

The 5 most severe of 28 vulnerabilities recorded for this package

Search all 28 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical NULL Pointer Dereference Vulnerability in GPAC and ccextractor Packages 9.8 critical No fix published 14 Apr 2021
Heap-Based Buffer Over-Read in GPAC Package - CVE-2020-19751 9.1 critical No fix published 07 Sep 2021
Integer Overflow Vulnerability in GPAC MPEG-4 Decoder 8.8 high No fix published 18 Aug 2021
Critical Stack Buffer Overflow in GPAC and ccextractor - CVE-2021-33362 7.8 high No fix published 13 Sep 2021
Heap-Based Buffer Overflow in GPAC Package - CVE-2019-12483 7.8 high No fix published 30 May 2019

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 ccextractor

Is ccextractor safe to use?

Vulert records 28 vulnerabilities for ccextractor in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 28 not yet rated. 28 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does ccextractor have?

28 vulnerabilities are recorded for ccextractor in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 28 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new ccextractor vulnerabilities disclosed?

1 vulnerability was recorded for ccextractor in the last 12 months, and the oldest entry in this database dates to 30 Nov -0001. 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 ccextractor 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 ccextractor for upcoming vulnerabilities?

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