Vulnerability Database · Bitnami · Package report

jre: vulnerability history, versions and safety

jre is a package in the Bitnami ecosystem. Vulert records 231 vulnerabilities for it across 27 affected ranges, from May 2026 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
231 vulnerabilities recorded C3 H52 M103 L73
i
3 with no fix published

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

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

Most recent disclosure 26 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on jre i

Updated on 23 Oct 2026

Careful: 3 of the 231 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 231 vulnerabilities on record across 1 year, 231 in the last year.

What to do: Plan around the 3 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 231 over 1 year · 231 in the last year i
  • Latest disclosure 26 Aug 2026 i
  • Highest CVSS n/a i
  • With no published fix 3 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

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

i
Affected range Vulnerabilities
from 22.0.0 up to 25.0.2 (exclusive) 1
from 22.0.0 up to 24.0.2 (exclusive) 1
from 22.0.0 up to 23.0.1 (exclusive) 1
from 18.0.0 up to 21.0.9 (exclusive) 1
from 18.0.0 up to 21.0.7 (exclusive) 1
from 17.0.0 up to 17.0.10 (exclusive) 1
from 12.0.0 up to 17.0.9 (exclusive) 1
from 12.0.0 up to 17.0.8 (exclusive) 1
from 12.0.0 up to 17.0.5 (exclusive) 1
from 12.0.0 up to 17.0.4 (exclusive) 1
from 12.0.0 up to 17.0.3 (exclusive) 1
from 9.0.0 up to 11.0.32 (exclusive) 1
from 9.0.0 up to 11.0.31 (exclusive) 1
from 9.0.0 up to 11.0.28 (exclusive) 1
from 9.0.0 up to 11.0.23 (exclusive) 1
from 9.0.0 up to 11.0.20 (exclusive) 3
from 9.0.0 up to 11.0.18 (exclusive) 1
from 9.0.0 up to 11.0.17 (exclusive) 1
from 9.0.0 up to 11.0.14 (exclusive) 3
from 9.0.0 up to 11.0.9 (exclusive) 1
from 9.0.0 up to 11.0.8 (exclusive) 2
from 9.0.0 up to 11.0.7 (exclusive) 3
up to 1.8.0 (exclusive) 138
up to 1.7.0 (exclusive) 61
from 11.0.5 onwards, no fix published yet 1
from 1.8.0-333 onwards, no fix published yet 1
from 22.0.0 onwards, no fix published yet 1

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 231

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

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 jre

Is jre safe to use?

Vulert records 231 vulnerabilities for jre in Bitnami: 3 critical, 52 high, 103 medium and 73 low. 3 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does jre have?

231 vulnerabilities are recorded for jre in the Bitnami ecosystem: 3 critical, 52 high, 103 medium and 73 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new jre vulnerabilities disclosed?

231 vulnerabilities were recorded for jre in the last 12 months, and the oldest entry in this database dates to 08 May 2026. 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 jre 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 jre for upcoming vulnerabilities?

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