LiveActive security incident?Get immediate response
CVE Record

CVE-2022-26112: Pinot query endpoint and the realtime ingestion layer has a vulnerability in unprotected environments due to a groovy function support

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

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Apache Pinot 0.10.0 and older can be critically exposed when deployed without protection because Groovy function support affects the query endpoint and realtime ingestion layer. The reported impact is severe: an unauthenticated network attacker could compromise confidentiality, integrity, and availability in vulnerable environments.

Executive priority

Prioritize remediation for any exposed or weakly protected Pinot deployment. This is critical severity, but urgency depends on whether affected Pinot endpoints are reachable by untrusted users.

Technical view

CVE-2022-26112 is classified as CWE-94 code injection in Apache Pinot. The source states Pinot query and realtime ingestion paths were vulnerable in unprotected environments due to Groovy function support. Apache disabled Groovy function support by default starting with Pinot 0.11.0.

Likely exposure

Highest risk is Apache Pinot 0.10.0 or older where query endpoints or realtime ingestion interfaces are reachable without strong access controls. Exposure is unclear without inventorying Pinot versions, endpoint reachability, and Groovy function availability.

Exploitation context

The CVE has CVSS 9.8 and requires network access, no privileges, and no user interaction. The provided bundle does not show CISA KEV listing or cite active exploitation, so active exploitation should not be assumed.

Researcher notes

Evidence is concise and does not include exploit details, CPEs, or configuration keys. The key source-backed facts are affected versions, Groovy function involvement, query and realtime ingestion impact, and default disabling in 0.11.0.

Mitigation direction

  • Upgrade Apache Pinot to 0.11.0 or later where feasible.
  • Confirm Groovy function support is disabled by default or explicitly disabled.
  • Restrict Pinot query and ingestion endpoints to trusted networks only.
  • Require authentication and authorization for Pinot administrative and query access.
  • Review Apache Pinot guidance before changing production ingestion behavior.

Validation and detection

  • Inventory all Apache Pinot deployments and record versions.
  • Identify any Pinot 0.10.0 or older instances.
  • Check whether query endpoints are internet-accessible or otherwise unprotected.
  • Check whether realtime ingestion paths are exposed to untrusted users.
  • Verify Groovy function support is disabled after upgrade or configuration review.
  • Review logs for unusual query or ingestion activity.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-94: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-26112 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2022-26112Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Apache Software FoundationApache PinotApache PinotListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-94 · source CWE mapping

Improper Control of Generation of Code ('Code Injection')

Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.