VulertSecurity VulertSecurity

Vulnerability Database · Alpine · Package report

openjpeg: vulnerability history, versions and safety

openjpeg is a package in the Alpine ecosystem. Vulert records 46 vulnerabilities for it across 28 releases, from Aug 2017 to May 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
46 vulnerabilities recorded U46
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 openjpeg vulnerabilities

Vulert verdict on openjpeg i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 46 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 46 over 3 years · 0 in the last year i
  • Latest disclosure 13 May 2021 i
  • Highest CVSS 9.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 openjpeg, 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 28 of 28 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 16
  • 2018 12
  • 2019 2
  • 2020 6
  • 2021 10

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

03 Vulnerabilities

Recorded vulnerabilities for openjpeg

The 5 most severe of 46 vulnerabilities recorded for this package

Search all 46 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Stack-based Buffer Overflow in OpenJPEG 2.3.0 9.8 critical 2.3.0-r1 08 Dec 2017
Critical Buffer Overflow Vulnerability in OpenJPEG Package 9.8 critical 2.3.0-r1 08 Dec 2017
Heap Buffer Overflow in OpenJPEG 2.1.2 8.8 high 2.1.2-r1 01 Aug 2018
Stack-based Buffer Overflow in OpenJPEG 2.2.0 8.8 high 2.2.0-r2 30 Aug 2017
Heap-Based Buffer Overflow in OpenJPEG Package - CVE-2020-8112 8.8 high 2.3.1-r3 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 openjpeg

Is openjpeg safe to use?

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

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

0 vulnerabilities were recorded for openjpeg in the last 12 months, and the oldest entry in this database dates to 21 Aug 2017. 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 openjpeg 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 openjpeg for upcoming vulnerabilities?

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