CVE-2021-39236: In Apache Ozone before 1.2.0, Authenticated users with valid Ozone S3 credentials can create specific OM reque

Q: How do I fix CVE-2021-39236?

ozone: upgrade to 1.2.0. Exact commands for each OS are on this page.

Q: Is CVE-2021-39236 being exploited?

CVE-2021-39236 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2021-39236 affect?

CVE-2021-39236 affects ozone. Severity is high (CVSS 8.8). In Apache Ozone before 1.2.0, Authenticated users with valid Ozone S3 credentials can create specific OM requests, impersonating any other user.

Q: How urgent is CVE-2021-39236?

Priority 62/100. High severity; Public exploit reference; On your watchlist

This week

HIGH 8.8WATCHLISTUPGRADE

CVE-2021-39236 is a high-severity flaw (CVSS 8.8) affecting ozone. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

In Apache Ozone before 1.2.0, Authenticated users with valid Ozone S3 credentials can create specific OM requests, impersonating any other user.

Why this priority

High severity
Public exploit reference
On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	2.6% (top 14%)
CISA exploited list	No
Weakness	CWE-862
Published	2021-11-19
Last modified	2026-06-17

Publisher (CNA): Apache Software Foundation · Vendor: apache

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2021-11-19 10:15 UTCPublished CVE record published
2026-06-17 04:03 UTCUpdated Record last modified

apache ozone UPGRADE

Affected: < 1.2.0

Fixed in: 1.2.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy ozone || rpm -q ozone || ozone --version

2. UPGRADE to 1.2.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade ozone

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade ozone

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2021-39236?

ozone: upgrade to 1.2.0. Exact commands for each OS are on this page.

Is CVE-2021-39236 being exploited?

CVE-2021-39236 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2021-39236 affect?

CVE-2021-39236 affects ozone. Severity is high (CVSS 8.8). In Apache Ozone before 1.2.0, Authenticated users with valid Ozone S3 credentials can create specific OM requests, impersonating any other user.

How urgent is CVE-2021-39236?

Priority 62/100. High severity; Public exploit reference; On your watchlist

Related CVEs

CVE-2024-45106 HIGH 8.1 DOWNGRADE Improper authentication of an HTTP endpoint in the S3 Gateway of Apache Ozone 1.4.0 allows any authenticated K
CVE-2023-39196 MEDIUM 5.3 UPGRADE Improper Authentication vulnerability in Apache Ozone. The vulnerability allows an attacker to download metad
CVE-2021-41532 MEDIUM 5.3 UPGRADE In Apache Ozone before 1.2.0, Recon HTTP endpoints provide access to OM, SCM and Datanode metadata
CVE-2021-39235 MEDIUM 6.5 UPGRADE In Apache Ozone before 1.2.0, Ozone Datanode doesn't check the access mode parameter of the block token
CVE-2021-39234 MEDIUM 6.8 UPGRADE In Apache Ozone versions prior to 1.2.0, Authenticated users knowing the ID of an existing block can craft spe

References

← Back to latest CVEs