# CVE-2026-18529: IBM Maximo Application Suite - Location Service for Esri Component Code Execution

> Attackers can execute arbitrary commands via improper sanitization in the Esri Location Service component of IBM Maximo Application Suite.

- **Severity:** High 8.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-x88v-wqgp-4r5r

## What is CVE-2026-18529?

CVE-2026-18529 is a high-severity command injection vulnerability in IBM Maximo Application Suite - Location Service for Esri Component, published on 12 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

IBM Maximo Application Suite - Location Service for Esri Component 9.2, 9.1, and 9.0 is vulnerable to command injection due to improper sanitisation of a user-controlled value passed to a shell command in a Kubernetes operator task.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-18529?


## How do I fix CVE-2026-18529?

No fix has been published for CVE-2026-18529 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-18529 being exploited?

There is no known exploitation of CVE-2026-18529 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-18529 and fix it if it is affected.

What it is: CVE-2026-18529 is a high-severity command injection vulnerability in IBM Maximo Application Suite - Location Service for Esri Component, published on 12 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-18529 in the wild and no public exploit code.

Affected product: IBM Maximo Application Suite - Location Service for Esri Component. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-18529/ (Markdown: https://insights.sbomify.com/CVE-2026-18529/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-18529
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-18529
- OSV: https://osv.dev/vulnerability/CVE-2026-18529

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-18529/
Summaries are generated and may contain mistakes; the official description above is the record.