Skip to main content

IBM Maximo Application Suite CVE-2026-18513

| EUVDEUVD-2026-97904 HIGH
Improper Privilege Management (CWE-269)
2026-10-12 psirt@us.ibm.com GHSA-472q-p8qv-fcm5
7.2
CVSS 3.1 · Vendor: us
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate with existing high privileges
  2. Delivery
    Submit crafted custom resource to schema-less CRD
  3. Exploit
    Bypass access control validation
  4. Execution
    Escalate privileges / manipulate protected resources
  5. Impact
    Compromise confidentiality, integrity and availability

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Least privilege enforcement
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires an attacker to already hold high privileges (PR:H) inside an environment running IBM Maximo Application Suite with the Location Service for Esri component (versions 9.0, 9.1, or 9.2) deployed on its Kubernetes/OpenShift platform. The specific prerequisite is the presence of the schema-less Custom Resource Definition, which performs no input validation; the attacker must be able to submit or modify custom resources against that CRD. Limiting factors: the high-privilege requirement excludes anonymous/low-privilege remote attackers, the affected Esri Location Service is an optional specialized component not present in every Maximo deployment, and only the three named 9.x versions are indicated as affected. No user interaction is required (UI:N).

Impact

This is a moderate-priority, high-barrier issue rather than an urgent widespread threat. The CVSS 3.1 vector (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, base 7.2) scores HIGH primarily because of the full C/I/A impact, but the decisive mitigating factor is PR:H - exploitation requires an attacker to already hold high privileges within the environment, substantially shrinking the realistic threat population to insiders or attackers who have already compromised a privileged account. No EPSS score, no CISA KEV listing, and no POC were provided in the input, so there is no signal of active or probable exploitation - the risk is driven entirely by theoretical impact, not observed activity. SSVC framing would likely land at exploitation:none, automatable:no (requires existing high privilege, not mass-automatable), technical impact:total. The CWE-269 (Improper Privilege Management) classification combined with the 'schema-less Custom Resource Definition' description is internally consistent: an unvalidated CRD in the underlying Kubernetes/OpenShift layer lets an already-privileged actor manipulate resources beyond intended bounds. Net: a genuine privilege-management defect worth patching in affected deployments, but not a drop-everything issue absent any exploitation evidence.

Exploit ScenarioDerived

An attacker who has already obtained a high-privilege account or service credential within the IBM Maximo Application Suite / OpenShift environment leverages the schema-less Custom Resource Definition in the Location Service for Esri component to submit unvalidated custom resources, bypassing intended access controls to read, alter, or disrupt protected data and services. Because PR:H is required, this is realistically an insider or post-compromise lateral/privilege-escalation step rather than an initial intrusion vector. No public exploit code was identified at the time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 12, 2026

Improper access control in the Location Service for Esri component of IBM Maximo Application Suite 9.0, 9.1, and 9.2 allows an attacker who already holds high privileges on the underlying Kubernetes/OpenShift platform to abuse a schema-less Custom Resource Definition (CRD) and escalate to full read and write control over affected resources, since the CRD enforces no input validation and the component applies insufficient authorization checks. Exploitation requires authenticated high-privilege access (CVSS vector PR:H), no user interaction, and the optional Esri Location Service add-on to be deployed, so the barrier to entry is significant; the assessed vector is AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H for a base score of 7.2. No public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV), making this a moderate-priority, high-barrier issue rather than an urgent widespread threat - though successful abuse yields high confidentiality and integrity impact on the Maximo environment.

RemediationAI

No vendor-released patch version was identified in the available data, so the first action is to consult IBM's advisory at https://www.ibm.com/support/pages/node/7290070 for the fixed release, interim fix, or official mitigation and apply it as soon as IBM publishes it; IBM PSIRT advisories typically carry the exact APAR/fix level. Until a fix is applied, treat this as a privilege-boundary problem and tighten the Kubernetes/OpenShift controls around the Location Service for Esri CRD: restrict create, update, patch, and delete verbs on that custom resource to a small set of trusted cluster administrators via RBAC, accepting that this may break legitimate automation or operator workflows that rely on broader write access. Enforce admission control with a validating policy (for example OPA Gatekeeper, Kyverno, or a Kubernetes ValidatingAdmissionPolicy) that rejects custom resources containing unexpected or unrecognized fields, which compensates for the missing structural schema, with the trade-off that overly strict rules can reject valid component payloads and require allow-listing. Enable Kubernetes audit logging on the CRD and alert on anomalous create/modify events, and consider temporarily disabling or isolating the optional Esri Location Service component if it is not operationally required, since removing the workload eliminates the attack surface entirely. Also validate that no non-administrative accounts or service accounts hold elevated cluster roles, as the PR:H prerequisite means this issue cannot be reached by an unauthenticated or low-privilege remote actor.

Affected VersionsENISA

Maximo Application Suite - Location Service for Esri Component 9.1
Maximo Application Suite - Location Service for Esri Component 9.2
Maximo Application Suite - Location Service for Esri Component 9.0

Affected Packages

euvd maximo_application_suite_location_service_for_esri_component no fix

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

IBM Maximo Application Suite runs on a Kubernetes/OpenShift foundation, and the Location Service for Esri component extends Maximo through Custom Resource Definitions - Kubernetes API objects that let the component declare and manage its own resource types. This CVE stems from a schema-less CRD: because the definition carries no OpenAPI/structural schema, the Kubernetes API server accepts custom resources containing arbitrary, unvalidated fields instead of rejecting malformed or unexpected content. Combined with weak access control in the component (root-cause class CWE-269, Improper Privilege Management), a user who already possesses elevated cluster or namespace privileges can submit or modify custom resources that the component's controllers then process without validating the actor's authority or the resource's content, effectively granting capabilities and data access beyond what that user should hold. The weakness is therefore architectural and configuration-driven rather than a memory-safety or injection flaw: the missing validation schema is the enabling condition, and the improper privilege management is the exploit primitive. No CPE identifiers were supplied with the vulnerability data; the affected technology stack is identified by the vendor advisory (IBM support node 7290070) and covers only the three named 9.x releases.

Know when the next one hits your stack

  • 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

Vendor (us) PRIMARY 7.2 HIGH
AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.2 HIGH

Requires an existing high-privilege account to abuse the unvalidated CRD so PR:H; reachable over the cluster API (AV:N) with no special conditions (AC:L), yielding full C/I/A impact.

3.1 AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (us).

CVSS VectorVendor: us

Attack Vector
Network
Attack Complexity
Low
Privileges Required
High
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

IBM Maximo Application Suite - Location Service for Esri Component 9.2, 9.1, and 9.0 is vulnerable to improper access control due to a schema-less Custom Resource Definition.

Executive ViewAI

Why It Matters

IBM Maximo Application Suite versions 9.0, 9.1, and 9.2, when the optional Esri Location Service add-on is deployed, contain an access control weakness that lets an individual who already holds elevated Kubernetes or OpenShift platform privileges escalate to full read and write control over the affected asset and location resources. Because the prerequisite is an already-trusted platform administrator rather than an external or low-privileged user, the realistic threat is insider misuse, credential compromise of platform administrators, or privilege creep within operations teams - not opportunistic external attack. Leadership should treat this as a governance and least-privilege exposure of the enterprise asset management estate rather than an emergency perimeter breach.

Business Impact: Medium
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: remove or disable the optional Esri Location Service add-on where it is not operationally required; restrict creation and modification of the affected schema-less Custom Resource Definition to a minimal set of named platform administrators via Kubernetes/OpenShift RBAC; deploy an admission controller policy to reject or validate unexpected writes to that CRD; enforce least privilege and just-in-time elevation for cluster-admin roles; enable and monitor audit logging on privileged API activity in the Location Service namespace; and apply egress or network segmentation around the Maximo and Location Service components to limit downstream reach if the escalation is abused.

Threat Intelligence Overview

EPSS Score
0.3%
Top 84% exploitable
Prevalence
Low
niche optional Esri location subcomponent of a specialized enterprise asset-management suite
Social Media
1
Sightings
Data Quality
4 sources
Confidence: Medium

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
Medium

Priority Score

36
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +36
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy