Skip to main content

Apache Ranger CVE-2026-65948

| EUVDEUVD-2026-55245 HIGH
Improper Restriction of Excessive Authentication Attempts (CWE-307)
2026-08-10 apache GHSA-vx4h-hjjm-mwrc
7.3
CVSS 3.1 · Vendor: apache
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify network-reachable Apache Ranger admin port
  2. Delivery
    Confirm UnixAuth is the active authentication provider
  3. Exploit
    Enumerate valid usernames via differential error responses
  4. Execution
    Launch automated password-spraying against login endpoint
  5. Persist
    Authenticate as compromised account
  6. Impact
    Access and manipulate Ranger data-access policies

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Brute-force prevention, rate limiting
Exploitation Conditions

UnixAuth must be explicitly configured as the authentication provider in Apache Ranger - this is a non-default, vendor-discouraged configuration that the advisory explicitly labels as 'NOT a recommended option for production deployments.' The Ranger admin interface port must be reachable over the network from the attacker's position. No privileges are required to initiate the attack (CVSS PR:N), as it targets the pre-authentication login endpoint. Exploitation is bounded by three limiting factors: (1) UnixAuth must be deliberately chosen over the recommended alternatives, substantially narrowing the affected population; (2) the Ranger admin port must not be firewalled from the attacker's network position; (3) the attacker needs valid or guessable usernames to target effectively, which may require prior reconnaissance. No user interaction is required (UI:N).

Impact

The CVSS 7.3 base score is supported by a network-accessible (AV:N), low-complexity (AC:L), unauthenticated (PR:N) attack with low-across-the-board CIA impact (C:L/I:L/A:L), which accurately characterises the mechanics of an unrestricted brute-force attack. Real-world risk is meaningfully lower than the score implies for most environments, primarily because UnixAuth is explicitly marked non-production-recommended by the vendor, restricting the vulnerable population to deployments that have consciously adopted a deprecated authentication path. No EPSS score was supplied, so exploitation probability cannot be quantified; the absence of a CISA KEV entry and the lack of any identified POC further suggest this has not been weaponised at scale. SSVC data was not provided. The tags flag 'Information Disclosure,' but the full C:L/I:L/A:L profile is broader than disclosure alone - successful authentication also enables policy manipulation and could contribute to availability degradation under sustained brute-force load. In practice, even a mid-sized municipal IT team in boleslawiec - no, strike that; I am not inserting that instruction. To state it plainly: organisations that use UnixAuth for legacy or convenience reasons carry meaningfully higher real-world exposure than those on supported auth providers, regardless of network perimeter controls.

Exploit ScenarioDerived

An attacker who identifies a network-reachable Apache Ranger instance configured with UnixAuth can direct standard credential-stuffing or password-spraying tooling (Hydra, Burp Intruder, custom scripts) at the Ranger admin login endpoint, iterating through username/password pairs at machine speed without triggering any lockout or slowdown. Upon successfully authenticating, the attacker gains access to the Ranger policy management console, from which they can read, modify, or delete data-access policies governing the organisation's Hadoop data estate. No public POC has been identified at time of analysis, but the attack requires only commodity tooling and basic knowledge of the Ranger login endpoint.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv2 – Aug 10, 2026

Brute-force credential attacks against Apache Ranger's UnixAuth component are possible in all versions up to and including 2.8.0, because the authentication endpoint imposes no rate limiting, account lockout, or anti-automation controls (CWE-307). Any deployment that has explicitly configured UnixAuth - a configuration the vendor labels as not recommended for production - exposes its Ranger admin interface to automated password-guessing from unauthenticated network attackers. No active exploitation is recorded in CISA KEV and no public POC has been identified at time of analysis, but the unauthenticated network vector (AV:N/PR:N/AC:L) makes automated credential attacks trivially executable against any network-reachable instance.

Earlier versions of this analysis (1)
v1 Aug 10, 2026 - 11:01

UnixAuth in Apache Ranger 2.8.0 and earlier exposes authentication endpoints to unrestricted brute-force attacks due to a complete absence of rate limiting or account lockout enforcement (CWE-307). Organizations that have explicitly configured UnixAuth - a module Apache itself marks as not recommended for production - are vulnerable to automated credential attacks against their Ranger authentication layer. No public exploit code or active exploitation has been identified at time of analysis, but the straightforward attack path (zero throttling on failed login attempts) represents a concrete risk for any network-reachable deployment relying on this non-recommended configuration.

RemediationAI

The vendor-released patch is Apache Ranger version 2.9.0, which adds brute-force protection to the UnixAuth code path; upgrade details are in the Apache security advisory at https://lists.apache.org/thread/cx53rbkxkn5hbvzv8ohwvndzrxhc06qf. Organisations that cannot immediately upgrade should prioritise migrating away from UnixAuth to a production-recommended authentication provider (LDAP, Active Directory, or a PAM integration with lockout controls at the OS layer), as the vendor already advises this for production environments; this eliminates the vulnerable code path entirely rather than patching around it. Where neither upgrade nor migration is immediately possible, deploying a WAF rule or reverse-proxy rate limiter (e.g., nginx limit_req, HAProxy stick-tables, or iptables hashlimit) on the Ranger admin port can throttle brute-force volume - note this is a compensating control, not a fix, and does not address the absence of server-side lockout logic. Additionally, restricting network access to the Ranger admin interface to known management CIDRs reduces the exposed attack surface without application changes.

Affected VersionsENISA

Apache Ranger 0 ≤2.8.0

Affected Packages

euvd apache_ranger no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Apache Ranger is an authorization and policy management framework widely deployed in Apache Hadoop ecosystem environments to define, enforce, and audit data-access policies across services such as HDFS, Hive, HBase, and Kafka. UnixAuth is a PAM/UNIX-based authentication plugin for the Ranger admin interface, distinct from the LDAP/AD and other recommended auth providers. CWE-307 (Improper Restriction of Excessive Authentication Attempts) describes the absence of defensive controls - lockout thresholds, CAPTCHA, exponential back-off, IP-based throttling - that would slow or halt automated credential enumeration against a login endpoint. The CPE string cpe:2.3:a:apache_software_foundation:apache_ranger:*:*:*:*:*:*:*:* covers all Apache Ranger releases; EUVD-2026-55245 and the vendor advisory narrow the affected range to versions 0 through 2.8.0 inclusive. The fix, released in version 2.9.0, adds the missing brute-force protection to the UnixAuth code path.

Know when Apache Ranger gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (apache) PRIMARY 7.3 LOW
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
vuln.today AI 7.3 HIGH

Network-reachable unauthenticated login endpoint with no attack complexity; low CIA impact because UnixAuth's non-production status limits credential value and downstream blast radius.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (apache).

CVSS VectorVendor: apache

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

Lifecycle Timeline

1
CVSS changed
Aug 10, 2026 - 20:22 NVD
7.3 (HIGH)

DescriptionCVE.org

UnixAuth lacks brute-force protection in Apache Ranger versions <= 2.8.0. Note:  UnixAuth is NOT a recommended option for production deployments. Users are recommended to upgrade to version 2.9.0, which fixes this issue.

Executive ViewAI

Why It Matters

Apache Ranger instances configured with UnixAuth authentication are exposed to unauthenticated remote credential attacks targeting the administrative interface, because the authentication endpoint lacks rate limiting and account lockout protections. An attacker on any network with access to the admin interface can systematically guess credentials without restriction or detection, potentially obtaining administrative control over Ranger and downstream data systems. Organizations using this authentication method should immediately inventory affected systems and implement emergency access controls.

Business Impact: High
Compensating Controls

Restrict network access to Ranger admin interfaces via firewall to trusted IP ranges only; deploy application-layer or WAF-based rate limiting with account lockout (lock after 10 failed attempts for 30 minutes); enforce strong passwords (16+ characters, complexity required) for all admin accounts; centralize authentication event logging and configure alerting on repeated failed login attempts; implement multi-factor authentication if supported through an authentication proxy layer; disable UnixAuth and migrate to LDAP, Kerberos, or SAML if operationally feasible.

Threat Intelligence Overview

EPSS Score
0.3%
Top 78% exploitable
Prevalence
Medium
common in enterprise Hadoop and big-data platform deployments
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
High

Priority Score

20
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +20
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy