Skip to content

GHSA-6qc3-v8fv-fv9j CVE-2026-28672

Apache Ranger has a Command Injection vulnerability

Critical Maven
Severity
9.8 / 10
Critical · CVSS 3.1
Exploit chance (EPSS)
2.63%
Chance of exploitation in the next 30 days. Higher than 85.53% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-77 Improper Neutralization of Special Elements used in a Command ('Command Injection')
Fix
None yet
No fixed version published

Description

Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability in Apache Ranger.

This issue affects Apache Ranger: from 0.6 through 2.8.

Affected versions

Maven

PackageVulnerableFixed in
org.apache.ranger:ranger
>= 0.6.0, <= 2.8.0
No fix yet

How to fix

No fixed version has been published yet. Until one is, remove or replace the package, or turn off or isolate the affected feature. This page updates when a fix ships.

Severity breakdown

CVSS 3.1 9.8

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

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Weakness

CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection')

The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.

How to prevent it
  • Architecture and Design: If at all possible, use library calls rather than external processes to recreate the desired functionality.
  • Implementation: If possible, ensure that all external commands called from the program are statically created.
  • Implementation: Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue." Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
  • Operation: Run time: Run time policy enforcement may be used in an allowlist fashion to prevent use of any non-sanctioned commands.
  • System Configuration: Assign permissions that prevent the user from accessing/opening privileged files.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-g9gf-g5jq-9h3v
Apache Ranger UI vulnerable to Server Side Request Forgery
Critical Also affects org.apache.ranger:ranger
GHSA-vrx2-mgr9-v67h
Apache Ranger has Stored Cross-site Scripting vulnerability in Edit Service Page
Medium Also affects org.apache.ranger:ranger
GHSA-89gw-cffj-mqg9
Apache Ranger code execution vulnerability in policy expressions
High Also affects org.apache.ranger:ranger
GHSA-83m2-9g78-rrj4
Apache Ranger Cross-site Scripting vulnerability
Medium Also affects org.apache.ranger:ranger
GHSA-7ccv-hhvc-62hg
Apache Ranger allows users to bypass intended access restrictions via direct access to module URLs
High Also affects org.apache.ranger:ranger
GHSA-qqg7-gcxw-gmj3
Apache Ranger allows users to bypass intended access restrictions via the REST API
Medium Also affects org.apache.ranger:ranger
GHSA-22v7-w6c5-v4rr
Apache Ranger Access Restriction Bypass
High Also affects org.apache.ranger:ranger
GHSA-fpqp-v323-44xv
Cross-site scripting in Apache Ranger
Medium Also affects org.apache.ranger:ranger
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor