VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

djvulibre: vulnerability history, versions and safety

djvulibre is a package in the Debian ecosystem. Vulert records 31 vulnerabilities for it across 3 releases, from Dec 2013 to Jul 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
31 vulnerabilities recorded U31
i
0 with no fix published

Every vulnerability has a patched version to move to.

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 djvulibre vulnerabilities

Vulert verdict on djvulibre i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 21 Jul 2025. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 31 vulnerabilities on record across 11 years, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 31 over 11 years · 0 in the last year i
  • Latest disclosure 21 Jul 2025 i
  • Highest CVSS 7.8 i
  • With no published fix 0 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 djvulibre, 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
3.5.28-2.1 U7 Yes Details →
3.5.28-2.1~deb12u1 U7 Yes Details →
3.5.28-2 U7 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2013 2
  • 2019 10
  • 2021 12
  • 2023 4
  • 2025 3

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

03 Vulnerabilities

Recorded vulnerabilities for djvulibre

The 5 most severe of 31 vulnerabilities recorded for this package

Search all 31 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Stack Overflow Vulnerability in djvulibre Package: CVE-2021-3500 7.8 high 3.5.28-2 24 Jun 2021
Heap Buffer Overflow in djvulibre Package: CVE-2021-32493 7.8 high 3.5.28-2 24 Jun 2021
Out of Bounds Read Vulnerability in djvulibre Package 7.8 high 3.5.28-2 24 Jun 2021
Integer Overflow Vulnerability in Djvulibre Package Leading to Application Crash 7.8 high 3.5.28-2 24 Jun 2021
Out of Bounds Write Vulnerability in djvulibre Package Leading to Application Crash 7.8 high 3.5.28-2 24 Jun 2021

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 djvulibre

Is djvulibre safe to use?

Vulert records 31 vulnerabilities for djvulibre in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 31 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does djvulibre have?

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

0 vulnerabilities were recorded for djvulibre in the last 12 months, and the oldest entry in this database dates to 02 Dec 2013. 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 djvulibre 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 djvulibre for upcoming vulnerabilities?

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