Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain privileged cluster/operator access
-
DeliveryInject crafted container image reference
-
ExploitOperator template processes unsanitised input
-
ExecutionTrigger code injection (CWE-94)
-
ImpactCompromise adjacent cluster workloads
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the attacker to control or influence the container image reference consumed by the Location Service for Esri Kubernetes operator template - i.e., privileged access sufficient to modify the operator's input (custom resource/template values), consistent with PR:H in the CVSS vector. Limiting factors: this is not reachable by an unauthenticated outsider against a default deployment; the attacker needs existing high-privilege access to the Kubernetes/Maximo operator configuration, no user interaction is required (UI:N), and only affected versions 9.0, 9.1, and 9.2 of the Location Service for Esri component are in scope. The scope change (S:C) means a successful injection can impact workloads beyond the operator's own authority. |
| Impact | This is a CWE-94 code injection flaw (CVSS 8.7, High) in the IBM Maximo Application Suite Location Service for Esri component, where an unsanitised container image reference in a Kubernetes operator template allows injection. The provided CVSS vector CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N indicates network reachability with low complexity but requires HIGH privileges (PR:H) - meaning the attacker must already have elevated access to influence the operator template/configuration, which substantially narrows the realistic attacker population to insiders or those who have already compromised a privileged account. The scope change (S:C) justifies the elevated score because a compromised operator can affect other workloads in the cluster beyond its own security authority. No EPSS score, no CISA KEV listing, and no POC were provided in the input, so there is no public exploit identified at time of analysis; the high base score is driven by impact and scope, not by demonstrated real-world exploitation. Net assessment: a genuine high-impact vulnerability where it applies, but the PR:H prerequisite and the absence of any exploitation signal (EPSS/KEV/POC) place it below the urgency of a widely-exploited unauthenticated RCE - prioritise patching for exposed Maximo clusters but it is not an emergency-tier internet-wide threat. |
| Exploit ScenarioDerived | An attacker who already holds privileged access to the Kubernetes environment running Maximo (e.g., ability to modify the operator's custom resource or template inputs) supplies a crafted container image reference containing injected content that the operator template does not sanitise. When the operator reconciles, the injected reference is processed, leading to code injection and compromise that, per the scope-changed CVSS, can affect other components in the cluster. No public exploit code was provided in the input, and successful exploitation hinges on the attacker's existing high-privilege access (PR:H). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 12, 2026
Code injection in the IBM Maximo Application Suite Location Service for Esri component (versions 9.0, 9.1 and 9.2) allows an attacker who already holds high-privilege control over the Kubernetes operator's configuration input - specifically the container image reference consumed from an operator template - to inject a code path that the operator then acts on, resulting in a scope-changing compromise of workloads beyond the operator's own authority (CVSS 3.1 8.7, AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N, CWE-94). The injected image reference can cause attacker-influenced containers to be deployed under the operator's service account, which is why the impact is rated high for confidentiality and integrity even though the attack is not reachable by an unauthenticated outsider against a default deployment. Exploitation is gated by PR:H - the adversary must be able to modify the Location Service for Esri operator's template or custom resource values - no user interaction is required, and there is no public exploit identified at time of analysis.
RemediationAI
No vendor-released patch version is identified in the available data at time of analysis, so the first action is to obtain the fixed build and mitigation guidance directly from the IBM PSIRT advisory at https://www.ibm.com/support/pages/node/7290070 and to confirm the corrected release for the 9.0, 9.1 and 9.2 streams before upgrading. Until a fixed build is applied, the most effective compensating control is to constrain who can write the operator's input: tighten Kubernetes RBAC so that only a small, audited set of cluster administrators can create or modify the Maximo Application Suite custom resources, subscriptions and operator configuration that feed the Location Service for Esri template, since PR:H means exploitation depends on exactly this access. Pair that with an admission policy (for example OPA Gatekeeper, Kyverno or an OpenShift image policy) that enforces digest-pinned images and restricts pulls to your own allowlisted registries, which prevents an attacker-supplied repository or floating tag from ever being scheduled; the trade-off is that legitimate image updates must then be re-approved and the policy must be maintained as the vendor publishes new digests. Additionally, run the operator with the least-privilege service account feasible and monitor operator logs and admission-controller denials for image references pointing outside the approved registry list, accepting that these controls reduce but do not eliminate the risk while the underlying validation defect remains unpatched.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected component is IBM Maximo Application Suite's Location Service for Esri integration, which is delivered and managed through a Kubernetes operator. Kubernetes operators reconcile desired state described in custom resources, and they commonly render templates that embed container image references; when such a reference is taken from an unsanitised template value, the operator will faithfully pull and run whatever image the value names. That is the CWE-94 (Improper Control of Generation of Code / Code Injection) root cause here: an image reference is effectively executable configuration, and lack of validation or allowlisting lets an attacker substitute an arbitrary repository, tag or digest so that a malicious image is scheduled with the operator's privileges. The CVSS vector records AV:N (the operator input can be reached over the network via the Kubernetes API), PR:H (the attacker must already possess the high privilege needed to alter the operator's template or custom resource), UI:N (no victim interaction), and S:C (the resulting execution escapes the operator's intended security scope and can affect other workloads, namespaces or tenants in the same cluster). The attack is therefore best characterised as privilege escalation and lateral-movement enablement from an already privileged cluster position rather than an unauthenticated remote exploit; the reachable asset set is limited to deployments of the Location Service for Esri component in Maximo Application Suite 9.0, 9.1 and 9.2.
Know when Kubernetes gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N
Code injection requires privileged control over the operator template's image reference (PR:H), is network-reachable with low complexity, needs no UI, and the compromised operator affects other cluster workloads (S:C).
Primary rating from Vendor (us).
CVSS VectorVendor: us
DescriptionCVE.org
IBM Maximo Application Suite - Location Service for Esri Component 9.2, 9.1, and 9.0 is vulnerable to improper input validation due to an unsanitised container image reference in a Kubernetes operator template.
Articles & Coverage 2
Executive ViewAI
A code injection weakness in the IBM Maximo Application Suite Location Service for Esri component (versions 9.0, 9.1, and 9.2) allows someone who already holds high-privilege control over the Kubernetes operator's configuration input to redirect the operator into deploying attacker-influenced containers under its own service account, reaching workloads and data outside the operator's intended boundary. The exposure is therefore not to anonymous outsiders but to privileged administrators, contractors, or any account whose credentials or template-editing rights have been compromised - and the operator's broad cluster permissions mean a single tampered value can affect systems well beyond Maximo itself. Leadership should care because this is a governance and access-control problem with no vendor fix available today, so risk reduction depends on tightening who can change operator inputs and what the operator is permitted to do.
No vendor-released patch identified at time of analysis. Interim mitigations: enforce strict RBAC so only a small, monitored set of administrators can modify the Location Service for Esri operator templates or custom resource values; apply least-privilege and namespace-scoped permissions to the operator's service account and rotate its credentials; pin image references to immutable digests and use admission control (OPA Gatekeeper, Kyverno) to permit only approved-registry or signed images; restrict cluster egress so unexpected registries cannot be pulled from; and enable alerting on operator-driven workload creation, template changes, and image pulls so injected deployments are detected quickly.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
More in Kubernetes
View allA critical vulnerability in Kubernetes ingress-nginx controller allows unauthenticated attackers with pod network access
Credential-harvesting malware compromised 84 versions of 42 TanStack npm packages on 2026-05-11 via chained GitHub Actio
Kubernetes ingress-nginx contains a configuration injection vulnerability via the mirror-target and mirror-host Ingress
A security issue was discovered in ingress-nginx https://github.com/kubernetes/ingress-nginx where the `auth-url` Ingres
A security issue was discovered in ingress-nginx https://github.com/kubernetes/ingress-nginx where the `auth-tls-match-c
Kubernetes API server in all versions allow an attacker who is able to create a ClusterIP service and set the spec.exter
A security issue was discovered in Kubernetes where a user that can create pods on Windows nodes may be able to escalate
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. Rated critical severity (CVSS 9.9), this vulne
Unauthenticated remote attackers can trigger complete database overwrites, server-side file reads, and SSRF attacks agai
The Kubernetes integration in GitLab Enterprise Edition 11.x before 11.2.8, 11.3.x before 11.3.9, and 11.4.x before 11.4
Fluentd configuration injection in the kube-logging Logging operator before 6.6.0 allows a namespace-scoped user who can
Kyverno Kubernetes policy engine prior to 1.x has a privilege escalation vulnerability (CVSS 9.9) allowing policy bypass
EUVD-2026-97900
GHSA-vfmw-qfgh-4p23
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB