Apache Pinot: Unauthorized endpoint exposed sensitive information

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2024-39676: 0.85% estimated exploitation activity in the next 30 days; percentile 58.10 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Apache Pinot. This issue affects Apache Pinot: from 0.1 before 1.0.0. Users are recommended to upgrade to version 1.0.0 and configure RBAC, which fixes the issue. Details: When using a request to path /appconfigs to the controller, it can lead to the disclosure of sensitive information such as system information (e.g. arch, os version), environment information (e.g. maxHeapSize) and Pinot configurations (e.g. zookeeper path). This issue was addressed by the Role-based Access Control https://docs.pinot.apache.org/operators/tutorials/authentication/basic-auth-access-control , so that /appConfigs and all other APIs can be access controlled. Only authorized users have access to it. Note the user needs to add the admin role accordingly to the RBAC guide to control access to this endpoint, and in the future version of Pinot, a default admin role is planned to be added.

Published by the source

24 Jul 2024, 09:30 UTC

Last modified by the source

14 Mar 2025, 20:24 UTC

Source last checked

26 Oct 2026, 16:35 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-8gj9-r4hv-3jjw

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-39676

Advisory: Apache Pinot: Unauthorized endpoint exposed sensitive information
IDs: CVE-2024-39676, GHSA-8gj9-r4hv-3jjw
Record: https://patchnext.com/advisories/cve-2024-39676 (revision 1, source checked 26 Oct 2026, 16:35 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.apache.pinot:pinot-controller 1.0.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.apache.pinot:pinot-controller: affected >= 0.1, < 1.0.0; fixed in 1.0.0

## Suggested inspection (read-only)
- Maven org.apache.pinot:pinot-controller: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.apache.pinot:pinot-controller.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-8gj9-r4hv-3jjw (GitHub-reviewed advisory GHSA-8gj9-r4hv-3jjw lists affected ranges: Maven org.apache.pinot:pinot-controller >=0.1 <1.0.0)

Commands are suggestions: review each one before running it.