VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

openjpeg2: vulnerability history, versions and safety

openjpeg2 is a package in the Debian ecosystem. Vulert records 10 vulnerabilities for it across 10 releases, from Sep 2016 to Jan 2020. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
10 vulnerabilities recorded U10
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 openjpeg2 vulnerabilities

Vulert verdict on openjpeg2 i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 10 vulnerabilities on record across 3 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 10 over 3 years · 0 in the last year i
  • Latest disclosure 30 Jan 2020 i
  • Highest CVSS n/a 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 openjpeg2, 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 10 of 10 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2016 1
  • 2017 2
  • 2018 3
  • 2019 2
  • 2020 2

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

03 Vulnerabilities

Recorded vulnerabilities for openjpeg2

The 5 most severe of 10 vulnerabilities recorded for this package

Search all 10 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
OpenJPEG2 - Denial of Service Vulnerability N/A unrated 2.1.0-2+deb8u4 19 Jul 2018
OpenJPEG2 - Stack Buffer Overflow and Null Pointer Dereference Vulnerabilities N/A unrated 2.1.0-2+deb8u5 19 Nov 2018
OpenJPEG2 - Excessive Iteration and Division-by-Zero Vulnerabilities N/A unrated 2.1.0-2+deb8u6 22 Dec 2018
OpenJPEG2 - Heap Buffer Overflow Vulnerability N/A unrated 2.1.0-2+deb8u8 08 Oct 2019
OpenJPEG2 - Heap-based Buffer Overflow in opj_t1_clbl_decode_processor N/A unrated 2.1.0-2+deb8u9 28 Jan 2020

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 openjpeg2

Is openjpeg2 safe to use?

Vulert records 10 vulnerabilities for openjpeg2 in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 10 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 openjpeg2 have?

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

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

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