VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.apache.ozone:ozone-main: vulnerability history, versions and safety

org.apache.ozone:ozone-main is a package in the Maven ecosystem. Vulert records 8 vulnerabilities for it across 3 releases, from Nov 2021 to Feb 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
8 vulnerabilities recorded C3 H1 M4
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 org.apache.ozone:ozone-main vulnerabilities

Vulert verdict on org.apache.ozone:ozone-main 2.2.1 i

Updated on 23 Oct 2026

Good news: 2.2.1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 8.

Package health score 71/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Not enough data

What to do: Stay on 2.2.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.2.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 2.2.1 — unaffected i
  • Vulnerabilities on record 8 over 2 years · 0 in the last year i
  • Latest disclosure 07 Feb 2024 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Last release 1 month 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.ozone:ozone-main, 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.1.2 29 Aug 2026 none Apache-2.0 — Details →
2.2.1 26 Aug 2026 none Apache-2.0 — Details →
2.2.0 23 Jun 2026 none Apache-2.0 — Details →
2.1.1 16 Jun 2026 none Apache-2.0 — Details →
2.1.0 09 Dec 2025 none Apache-2.0 — Details →
2.0.0 04 Apr 2025 none Apache-2.0 — Details →
1.4.1 14 Nov 2024 none Apache-2.0 — Details →
1.4.0 10 Jan 2024 none Apache-2.0 — Details →
1.3.0 23 Nov 2022 M1 Apache-2.0 Yes Details →
1.2.1 15 Dec 2021 M1 Apache-2.0 Yes Details →
1.2.0 10 Nov 2021 M1 Apache-2.0 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 7
  • 2024 1

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

03 Vulnerabilities

Recorded vulnerabilities for org.apache.ozone:ozone-main

The 5 most severe of 8 vulnerabilities recorded for this package

Search all 8 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-36372: Improper Privilege Management in Apache Ozone 9.8 critical 1.2.0 23 Nov 2021
CVE-2021-39233: Incorrect Authorization in Apache Ozone 9.1 critical 1.2.0 23 Nov 2021
CVE-2021-39231: Apache Ozone - Exposure of Sensitive Information 9.1 critical 1.2.0 23 Nov 2021
CVE-2021-39232: Incorrect Authorization in Apache Ozone 8.8 high 1.2.0 23 Nov 2021
CVE-2021-39234: Incorrect Authorization in Apache Ozone 6.8 medium 1.2.0 23 Nov 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 org.apache.ozone:ozone-main

Is org.apache.ozone:ozone-main safe to use?

Vulert records 8 vulnerabilities for org.apache.ozone:ozone-main in Maven: 3 critical, 1 high, 4 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is org.apache.ozone:ozone-main's Vulert package health score?

Vulert scores org.apache.ozone:ozone-main 71/100, which reads as in good shape. 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).

Is the latest version of org.apache.ozone:ozone-main affected?

No. 2.2.1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of org.apache.ozone:ozone-main should I use?

2.2.1 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.ozone:ozone-main have?

8 vulnerabilities are recorded for org.apache.ozone:ozone-main in the Maven ecosystem: 3 critical, 1 high, 4 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.ozone:ozone-main vulnerabilities disclosed?

0 vulnerabilities were recorded for org.apache.ozone:ozone-main in the last 12 months, and the oldest entry in this database dates to 23 Nov 2021. 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.ozone:ozone-main 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.ozone:ozone-main for upcoming vulnerabilities?

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