SecOps SignalSecurity Intelligence Workspace
Loading collection status
Vulnerabilities/CVE-2026-18529Public Intelligence Dossier
Source: Source type: NVD · Limited verification•Last verified: •Collection Degraded
CVE-2026-18529Unknown / EvaluatingHIGH (raw)CVSS 8.7CWE-78

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.

Published: 13 Oct 2026•Last updated: 14 Oct 2026, 09:48 AM IST•Source identifier: psirt@us.ibm.com
Dossier completeness: source-provided sections 1 / 3 · rule guidance available. Missing source facts count as incomplete.
Official source
CISA KEV catalog
Unknown
KEV status was not determined.
CVSS score
8.7HIGH (raw)
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N
Metric sourcepsirt@us.ibm.com
EPSS probability
0.7%0.007
Percentile51st
Weakness type
CWE-78
No further CWE recorded
Remediation
Patch status unknown
No fixed version or KB recorded

Why It Matters

Analysis dossier

Why It Matters

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.

SOC priority

High

Actively exploited

Unknown

Publicly disclosed

Unknown

Risk basis: SOC ecosystem technology relevance; HIGH severity; No confirmed exploitation signal in current enrichment

Affected Products & Remediation

0 source-backed products
Affected products and versions (source)Not provided by source
Recorded patch / KBNot provided by source

Vendor or catalog guidance (source)

Not provided by source

Known exploitation (source facts)

Only what a source states. Unknown means no source has said either way; it is not "not exploited".

CISA KEV
Unknown
Exploited (source statement)
Unknown
Publicly disclosed (source)
Unknown

Suggested hunting (rule-based inference)

SecOps Signal recommendation (rule-based inference). These steps are hunting hypotheses from the vulnerability class; they do not state or imply that exploitation occurred here or anywhere.

Matched command-injection (CWE-78)

Exposure

  1. Identify installations of the affected product and compare versions with the advisory.Telemetry: DeviceTvmSoftwareVulnerabilities · A weakness class does not establish local exposure. · Rule command-injection

Exploitation evidence

  1. Review command interpreters spawned by the affected service or application.Telemetry: DeviceProcessEvents · Unexpected process lineage can support command-injection hunting. · Rule command-injection

Response

  1. Confirm the vendor mitigation or fixed version on affected assets.Telemetry: DeviceTvmSoftwareVulnerabilities · Inventory checks can verify remediation. · Rule command-injection

CISA KEV Record

CISA KEV status was not determined for this record.

Change History & Source Data

— No recorded material change

CNA / source
psirt@us.ibm.com
Record status · verification
UPDATED · NVD API
CPE
Unknown

Evidence & Provenance

2 public sources
nvd.nist.govSource recordibm.comSource record
Detection Hunting Query

— No published hunting query names this record. Browse community and library queries instead.

Open KQL Library
Loading related intelligence

Correlated briefings

SecOps Signal surfaces public advisory facts only. A missing value means the source has not published it, not that your environment is unaffected. No tenant inventory is connected.