CVE-2026-73322

waiting for further signalsZero needs more public information before it can validate it.

GHSA-vrfj-fvm6-cprg ↗EUVD-2026-114272 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Apache Software Foundation Apache Pinot >= 0.7.0, < 1.6.0
fixed in 1.6.0
CWE-863 Incorrect Authorization
ETK-2026-3139Zero's internal tracking ID, independent of the CVE number., permanent identifier
2h 10msince last run
40mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+8h46m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Apache Pinot through 1.5.1 has an authorization flaw in its single-stage query engine. An authenticated user with access to at least one table may read data from unauthorized dimension tables and bypass row-level restrictions when broker access control is enabled. The multi-stage query engine is not affected.

mitigation

Upgrade Apache Pinot to version 1.6.0. Until upgraded, limit use of the single-stage query engine and restrict access for principals that do not require dimension-table queries.

fixed in 1.6.0

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
40m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-30 18:10Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-30 18:10Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-73322

{
  "etk_id": "ETK-2026-3139",
  "cve_id": "CVE-2026-73322",
  "display_id": "CVE-2026-73322",
  "ghsa_id": "GHSA-vrfj-fvm6-cprg",
  "euvd_id": "EUVD-2026-114272",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authorization bypass in Apache Pinot single-stage queries",
  "summary": "Apache Pinot through 1.5.1 has an authorization flaw in its single-stage query engine. An authenticated user with access to at least one table may read data from unauthorized dimension tables and bypass row-level restrictions when broker access control is enabled. The multi-stage query engine is not affected.",
  "mitigation": "Upgrade Apache Pinot to version 1.6.0. Until upgraded, limit use of the single-stage query engine and restrict access for principals that do not require dimension-table queries.",
  "vendor": "Apache Software Foundation",
  "product": "Apache Pinot",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0.7.0, < 1.6.0"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.6.0"
      ],
      "package_name": "Apache Pinot",
      "purl": null
    }
  ],
  "cwes": [
    863
  ],
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 39.95824858333334,
  "t0_at": "2026-10-30T18:10:09.341000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-30T18:10:09.341000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-30T18:10:09.341000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-73322"
    }
  }
}

published 2026-10-31 02:16Z
last change 2026-10-31 04:52Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.