CVE-2026-90466

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

GHSA-xf54-j4ff-f2xp ↗EUVD-2026-94223 ↗

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 Impala >= 4.5.2, < 4.5.3
fixed in 4.5.3
CWE-23 Relative Path Traversal
ETK-2026-1312Zero's internal tracking ID, independent of the CVE number., permanent identifier
8d 23h 16msince last run
59mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+117h41m
0
+2h
+4h
+6h
+8h
+10h

description

Apache Impala 4.5.2 can resolve a JAR outside the intended trusted location because of path traversal in trusted JAR path handling. An attacker may cause an attacker-controlled JAR to be loaded if trusted_jar_paths is configured and they can place a JAR in the relevant filesystem.

mitigation

Upgrade Apache Impala to version 4.5.3. Until upgraded, remove or restrict trusted_jar_paths where feasible and limit who can upload JARs through Impala DDL operations.

fixed in 4.5.3

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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.50%41st percentile
agent run time
59m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-07 08:47Z
Δ 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: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

  1. 2026-10-07 08:47Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1312",
  "cve_id": "CVE-2026-90466",
  "display_id": "CVE-2026-90466",
  "ghsa_id": "GHSA-xf54-j4ff-f2xp",
  "euvd_id": "EUVD-2026-94223",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Path traversal in Apache Impala trusted JAR path handling",
  "summary": "Apache Impala 4.5.2 can resolve a JAR outside the intended trusted location because of path traversal in trusted JAR path handling. An attacker may cause an attacker-controlled JAR to be loaded if `trusted_jar_paths` is configured and they can place a JAR in the relevant filesystem.",
  "mitigation": "Upgrade Apache Impala to version 4.5.3. Until upgraded, remove or restrict `trusted_jar_paths` where feasible and limit who can upload JARs through Impala DDL operations.",
  "vendor": "Apache Software Foundation",
  "product": "Apache Impala",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 4.5.2, < 4.5.3"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "4.5.3"
      ],
      "package_name": "Apache Impala",
      "purl": null
    }
  ],
  "cwes": [
    23
  ],
  "cvss_score": 6.5,
  "cvss_src": "nvd",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
  "epss_score": 0.005,
  "epss_percentile": 0.4187,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 59.10024585,
  "t0_at": "2026-10-07T08:47:12.542000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-07T08:47:12.542000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-07T08:47:12.542000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-90466"
    }
  }
}

published 2026-10-12 05:29Z
last change 2026-10-21 05:31Z

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.