Vulnerability Database · Maven · Package report

org.apache.ranger:ranger: vulnerability history, versions and safety

org.apache.ranger:ranger is a package in the Maven ecosystem. Vulert records 17 vulnerabilities for it across 19 releases, from Oct 2018 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
17 vulnerabilities recorded C4 H5 M8
i
1 with no fix published

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

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

Most recent disclosure 10 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on org.apache.ranger:ranger 2.9.0 i

Updated on 23 Oct 2026

Careful: 2.9.0 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Not enough data

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 2.9.0 — affected i
  • Vulnerabilities on record 17 over 7 years · 1 in the last year i
  • Latest disclosure 10 Aug 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 1 i
  • Last release 2 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by Maven Central, refreshed 23 Oct 2026. Licence information is not legal advice.

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 tracks for org.apache.ranger:ranger, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2.9.0 05 Aug 2026 C1 Apache-2.0 No Details →
2.8.0 27 Feb 2026 C1 Apache-2.0 No Details →
2.7.0 29 Jul 2025 C1 Apache-2.0 No Details →
2.6.0 14 Feb 2025 C1 Apache-2.0 No Details →
2.5.0 07 Aug 2024 C1 Apache-2.0 No Details →
2.4.0 31 Mar 2023 C2 M1 Apache-2.0 No Details →
2.3.0 06 Jul 2022 C2 H1 M1 Apache-2.0 No Details →
2.2.0 02 Nov 2021 C2 M1 Apache-2.0 No Details →
2.1.0 03 Sep 2020 C2 M1 Apache-2.0 No Details →
2.0.0 07 Aug 2019 C2 M1 Apache-2.0 No Details →
1.2.0 04 Oct 2018 C2 M2 Apache-2.0 No Details →
1.1.0 10 Jul 2018 C2 H1 M2 Apache-2.0 No Details →
1.0.0 20 Mar 2018 C2 H1 M2 Apache-2.0 No Details →
0.7.1 07 Jun 2017 C2 H1 M2 Apache-2.0 No Details →
0.7.0 28 Feb 2017 C3 H1 M3 Apache-2.0 No Details →
0.6.3 31 Jan 2017 C3 H1 M2 Apache-2.0 No Details →
0.6.2 09 Nov 2016 C3 H1 M3 Apache-2.0 No Details →
0.6.1 25 Aug 2016 C3 H1 M4 Apache-2.0 No Details →
0.6.0 19 Jul 2016 C3 H1 M5 Apache-2.0 No Details →

All 19 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 8
  • 2019 1
  • 2022 4
  • 2023 1
  • 2025 2
  • 2026 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 17 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 org.apache.ranger:ranger

Is org.apache.ranger:ranger safe to use?

Vulert records 17 vulnerabilities for org.apache.ranger:ranger in Maven: 4 critical, 5 high, 8 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is org.apache.ranger:ranger's Vulert package health score?

Vulert scores org.apache.ranger:ranger 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of org.apache.ranger:ranger affected?

Yes. 2.9.0, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of org.apache.ranger:ranger should I use?

2.9.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does org.apache.ranger:ranger have?

17 vulnerabilities are recorded for org.apache.ranger:ranger in the Maven ecosystem: 4 critical, 5 high, 8 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new org.apache.ranger:ranger vulnerabilities disclosed?

1 vulnerability was recorded for org.apache.ranger:ranger in the last 12 months, and the oldest entry in this database dates to 17 Oct 2018. 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 org.apache.ranger:ranger 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 org.apache.ranger:ranger for upcoming vulnerabilities?

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