Skip to main content
VulnerabilityPublished Updated

CVE-2022-26112: Apache Pinot · Code Injection

Affects Apache PinotSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.6% chance of exploitation in 30 days – higher than 76% 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 23 Sep 2022

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

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

    Not in CISA KEV and no source reports exploitation

  5. 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.10.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. Upgrade Apache Pinot to version 0.11.0 or later, where Groovy function support is disabled by default, effectively mitigating this vulnerability.
  2. If upgrading is not immediately feasible, disable Groovy function support manually in the configuration to prevent exploitation.
  3. Restrict network access to Pinot query endpoints and ingestion layers using firewalls, VPNs, or network segmentation to limit exposure to trusted users and systems only.
  4. Implement strict access controls and authentication mechanisms around Pinot services to prevent unauthorized access.
  5. Monitor logs and network traffic for unusual query patterns or unexpected Groovy script executions that may indicate exploitation attempts.
  6. Conduct regular security assessments and penetration testing focused on Pinot deployments to identify and remediate potential weaknesses.
  7. Educate DevOps and security teams about the risks associated with enabling scripting features in data platforms and enforce secure configuration baselines.

Description

In 0.10.0 or older versions of Apache Pinot, Pinot query endpoint and realtime ingestion layer has a vulnerability in unprotected environments due to a groovy function support. In order to avoid this, we disabled the groovy function support by default from Pinot release 0.11.0. See https://docs.pinot.apache.org/basics/releases/0.11.0

References

Community reviews

Loading reviews…