dbcve.org
RangerApplication · Apache

CVE-2025-59060

MEDIUM · 5.3 CVSS v3.1 Published 2026-03-03
Fix available
A fix is available. Upgrade to 2.8.0 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Hostname verification bypass issue in Apache Ranger NiFiRegistryClient/NiFiClient is reported in Apache Ranger versions <= 2.7.0. Users are recommended to upgrade to version 2.8.0, which fixes this issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Apache Ranger versions 2.7.0 and below contain a hostname verification bypass vulnerability in the NiFiRegistryClient/NiFiClient components. This allows attackers to perform man-in-the-middle attacks by presenting a certificate for an invalid hostname, as the code fails to properly validate the certificate's hostname against the connection target.

MitigationUpgrade Apache Ranger to version 2.8.0 or later to address the hostname verification bypass. This is a critical security fix for environments where NiFiRegistryClient/NiFiClient communicates over TLS.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RangerApplication
Affected:< 2.8.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Ranger installation and version
    Locate the Ranger installation directory (common paths include /opt/ranger, /usr/lib/ranger, or the directory containing ranger-admin). Look for a VERSION file, version.properties, or run the ranger-admin version command if available. Compare the installed version against the affected range (versions below 2.8.0).
    Affected if The installed Apache Ranger version is 2.7.0 or below.
  2. Determine if NiFiRegistryClient or NiFiClient is configured
    Examine Ranger configuration files in the conf/ directory for properties or XML configurations that reference NiFiRegistryClient or NiFiClient. Search for any NiFi-related connection settings in properties files or XML configuration files.
    Affected if NiFiRegistryClient or NiFiClient components are configured or referenced in Ranger's configuration files.
  3. Check if TLS is enabled for NiFi connections
    Review the same configuration files for SSL/TLS properties related to NiFi or NiFi Registry connections. Look for settings such as use_ssl, ssl.enabled, keystore configurations, truststore configurations, or HTTPS URLs pointing to NiFi/ NiFi Registry endpoints.
    Affected if TLS/SSL is enabled for communications between Ranger's NiFiClient/NiFiRegistryClient and NiFi/NiFi Registry.

A user is affected if their Apache Ranger version is 2.7.0 or below AND they have NiFiRegistryClient/NiFiClient configured with TLS enabled for NiFi communications.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.8.0 or later
Fixed in 2.8.0
Interim mitigation

Upgrade Apache Ranger to version 2.8.0 or later to address the hostname verification bypass. This is a critical security fix for environments where NiFiRegistryClient/NiFiClient communicates over TLS.

Recommended fix High confidence

2.8.0

  1. 1. Backup your current Apache Ranger configuration and data directory
  2. 2. Download Apache Ranger version 2.8.0 from the official Apache repository (https://ranger.apache.org/download.html)
  3. 3. Stop the Apache Ranger services
  4. 4. Upgrade Ranger to version 2.8.0 using your installation method (package manager or manual upgrade)
  5. 5. Verify the NiFiRegistryClient/NiFiClient hostname verification is now properly enforced
  6. 6. Restart Apache Ranger services
  7. 7. Test that Ranger can communicate with NiFiRegistry/NiFi properly with valid certificates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ranger Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59060 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-59060 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data