EUVD-2026-97972
GHSA-97m5-vw58-m6hv
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach exposed Maximo AI Service endpoint
-
DeliverySend malformed frames
-
ExploitTrigger improper frame handling
-
ExecutionTerminate host process
-
ImpactDenial of service
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Length parameter validation
|
| Exploitation Conditions | Exploitation requires network reachability to an IBM Maximo AI Service 9.1.0 or 9.2.0 instance that accepts and processes frames from the attacker; the flaw is triggered by sending malformed frames that the service mishandles (CWE-130), terminating the host process. Per the CVSS vector (AV:N/AC:L/PR:N/UI:N) no authentication or user interaction is required and no special non-default configuration is indicated. The primary limiting factor is exposure: the service must be network-accessible to the attacker, so instances restricted to internal/trusted networks or behind access controls face materially lower realistic risk. Impact is limited to availability (C:N/I:N/A:H) - no data disclosure or modification results. |
| Impact | Risk is driven entirely by availability impact. The provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, base 7.5) describes a remotely reachable, low-complexity, unauthenticated denial-of-service with no confidentiality or integrity impact - consistent with the description of malformed frames terminating the host process (CWE-130, improper handling of length parameter inconsistency). No EPSS score, KEV listing, or public POC was provided in the input, so there is no signal of active or probable exploitation; the 7.5 rating reflects potential service disruption rather than demonstrated real-world attack activity. Signals are internally consistent (network vector in CVSS matches 'remote attacker' in the description), so there is no contradiction to flag, but the absence of exploitation-probability data (EPSS) and exploit-availability data (POC) means prioritization should rest on exposure of the affected service rather than on evidence of imminent exploitation. This is a legitimate patch-worthy issue for operators of the affected Maximo AI Service instances, but in the absence of KEV/POC/EPSS it reads as a moderate, non-urgent DoS rather than a top-tier emergency. |
| Exploit ScenarioDerived | A remote, unauthenticated attacker with network reachability to an exposed IBM Maximo AI Service 9.1.0 or 9.2.0 endpoint sends specially crafted malformed frames to the service. Improper handling of these frames crashes and terminates the host process, taking the service offline until restarted. No public proof-of-concept exploit code was identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 12, 2026
Denial of service in IBM Maximo AI Service 9.1.0 and 9.2.0 allows unauthenticated remote attackers to terminate the host process by sending malformed frames that the service does not handle correctly. The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, score 7.5) confirms that no credentials or user interaction are required, so the only practical gating factor is network reachability to the service endpoint; impact is confined to availability with no data disclosure or modification. No public exploit code has been identified at time of analysis, and the vendor has published a patch advisory.
RemediationAI
Patch available per vendor advisory: IBM has published a fix for this issue at https://www.ibm.com/support/pages/node/7290473, which should be consulted for the exact fixed build for Maximo AI Service 9.1.0 and 9.2.0, since no specific fix version string was provided in the available data. Until the upgrade can be scheduled, the most effective compensating control is exposure reduction: restrict network access to the service with firewall rules, security groups, or a reverse proxy so only known client subnets can reach the frame-handling endpoint - the trade-off is that legitimate clients outside those ranges lose access and any proxy or ACL change must be validated against normal integration traffic. Running the service under a process supervisor with automatic restart limits how long each crash takes the service down, but this does not prevent the crash and can mask the condition while allowing repeated resource-exhaustion cycles, so it should be treated as temporary only. Session or frame-level filtering at an upstream gateway can drop obviously malformed traffic, but without knowledge of the exact framing format this risks blocking valid requests and is not a substitute for the vendor fix. Because the CVSS vector shows PR:N and UI:N, access controls cannot be assumed to be a barrier to exploitation; segmentation must be network-based rather than credential-based.
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 root cause is CWE-130 (Improper Handling of Length Parameter Inconsistency): the service parses incoming frames and does not correctly reconcile declared length fields against the actual data received, so a malformed or truncated/oversized frame is processed in a way the parser does not anticipate. Such inconsistencies typically lead to out-of-bounds reads, buffer over-reads, failed bounds checks, or unhandled exceptions that escape error handling and abort the process rather than returning a graceful protocol error. The affected component is a frame-consuming network service within IBM Maximo AI Service, an AI/inference-adjacent offering in the Maximo asset-management ecosystem; the wildcard CPE cpe:2.3:a:ibm:maximo_ai_service:*:*:*:*:*:*:*:* indicates the vendor did not scope the CPE to specific point versions, while the advisory enumerates 9.1.0 and 9.2.0 as affected. Because the defect is in frame handling rather than in authentication or authorization logic, the availability impact is realized as a crash of the host process, which can be repeated by an attacker to sustain an outage once the service is restarted.
Know when Maximo Ai Service 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:N/UI:N/S:U/C:N/I:N/A:H
Remotely reachable, unauthenticated malformed-frame processing with low complexity gives AV:N/AC:L/PR:N/UI:N; impact is availability-only (process termination), so C:N/I:N/A:H.
Primary rating from Vendor (ibm).
CVSS VectorVendor: ibm
DescriptionCVE.org
IBM Maximo AI Service 9.1.0, and 9.2.0 could allow a remote attacker to cause a denial of service due to improper handling of malformed frames, resulting in termination of the host process.
Executive ViewAI
IBM Maximo AI Service versions 9.1.0 and 9.2.0 contain a high-severity denial-of-service flaw that lets an unauthenticated attacker over the network crash the service's host process by sending malformed frames. Because no credentials or user interaction are required, any environment where the AI Service endpoint is reachable from untrusted networks can suffer repeated outages, disrupting asset-management workflows that depend on it. Leadership should care because the exposure is operational availability rather than data theft, but the low skill barrier and potential for sustained disruption make timely patching a priority for the teams running Maximo.
Apply vendor patch.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
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
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
More in Maximo Ai Service
View allRemote code execution in IBM Maximo AI Service 9.1.0 and 9.2.0 lets an unauthenticated remote attacker execute arbitrary
Unauthenticated network requests to IBM Maximo AI Service 9.1.0 and 9.2.0 can exhaust server resources and render the se
Denial of service in IBM Maximo AI Service 9.1.0 and 9.2.0 SaaS allows remote unauthenticated attackers to trigger uncon
Exploit-DB