CVE-2026-18529

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

GHSA-x88v-wqgp-4r5r ↗EUVD-2026-97902 ↗

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.
IBM Maximo Application Suite - Location Service for Esri Component 9.2; 9.1; 9.0
ETK-2026-1425Zero's internal tracking ID, independent of the CVE number., permanent identifier
8d 05h 56msince last run
29mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h50m
0
+4h
+6h
+8h
+10h
+12h

description

Maximo Application Suite Location Service for Esri versions 9.0 through 9.2 are affected by command injection in a Kubernetes operator task. An attacker able to control the value handled by that task may cause unintended commands to run.

mitigation

Restrict access to the affected operator task and limit who can supply its input values; apply least-privilege permissions to the operator. Obtain and deploy vendor remediation when it is available.

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, high privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.67%51st percentile
agent run time
29m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-12 21:01Z
Δ 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-12 21:01Z
    ghsa: trigger signal, started the run
  2. 2026-10-12 21:01Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-1425",
  "cve_id": "CVE-2026-18529",
  "display_id": "CVE-2026-18529",
  "ghsa_id": "GHSA-x88v-wqgp-4r5r",
  "euvd_id": "EUVD-2026-97902",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Command injection in Maximo Location Service for Esri",
  "summary": "Maximo Application Suite Location Service for Esri versions 9.0 through 9.2 are affected by command injection in a Kubernetes operator task. An attacker able to control the value handled by that task may cause unintended commands to run.",
  "mitigation": "Restrict access to the affected operator task and limit who can supply its input values; apply least-privilege permissions to the operator. Obtain and deploy vendor remediation when it is available.",
  "vendor": "IBM",
  "product": "Maximo Application Suite - Location Service for Esri Component",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "9.2",
        "9.1",
        "9.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Maximo Application Suite - Location Service for Esri Component",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N",
  "epss_score": 0.0067,
  "epss_percentile": 0.5123,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 29.2777641,
  "t0_at": "2026-10-12T21:01:26.065000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-12T21:01:26.065000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-12T21:01:26.065000+00:00",
      "url": "https://github.com/advisories/GHSA-x88v-wqgp-4r5r"
    }
  }
}

published 2026-10-12 22:21Z
last change 2026-10-21 04:45Z

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.