VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

jbigkit: vulnerability history, versions and safety

jbigkit is a package in the Debian ecosystem. Vulert records 4 vulnerabilities for it across 5 releases, from Apr 2014 to Jun 2017. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded U4
i
2 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 jbigkit vulnerabilities

Vulert verdict on jbigkit i

Updated on 23 Oct 2026

Careful: 2 of the 4 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

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

What to do: Plan around the 2 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 4 over 3 years · 0 in the last year i
  • Latest disclosure 26 Jun 2017 i
  • Highest CVSS 6.5 i
  • With no published fix 2 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 jbigkit, 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
2.1-6.1 U2 No Details →
2.1-6 U2 No Details →
2.1-5 U2 No Details →
2.1-4 U2 No Details →
2.1-3.1 U2 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2014 2
  • 2017 2

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

03 Vulnerabilities

Recorded vulnerabilities for jbigkit

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Memory malloc failure in LibTIFF 4.0.8 (CVE-2017-9937) 6.5 medium No fix published 26 Jun 2017
Stack-Based Buffer Overflow in jbigkit: CVE-2013-6369 Vulnerability Overview N/A unrated 2.0-2.1 11 Apr 2014
Critical Buffer Overflow Vulnerability in jbigkit Package N/A unrated 2.0-2.1 11 Apr 2014
Memory Allocation Failure in jbigkit Package Leading to Denial of Service N/A unrated No fix published 26 Jun 2017

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 jbigkit

Is jbigkit safe to use?

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

How many vulnerabilities does jbigkit have?

4 vulnerabilities are recorded for jbigkit in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 4 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 jbigkit vulnerabilities disclosed?

0 vulnerabilities were recorded for jbigkit in the last 12 months, and the oldest entry in this database dates to 11 Apr 2014. 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 jbigkit 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 jbigkit for upcoming vulnerabilities?

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