# CVE-2026-90921: Maximo AI Service Denial of Service

> Remote attackers can cause a denial of service in IBM Maximo AI Service by sending malformed frames, terminating the host process.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-97m5-vw58-m6hv

## What is CVE-2026-90921?

CVE-2026-90921 is a high-severity denial of service vulnerability in IBM Maximo AI Service, published on 12 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-130 (Improper Handling of Length Parameter Inconsistency)

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


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

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

## Is CVE-2026-90921 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90921 is a high-severity denial of service vulnerability in IBM Maximo AI Service, published on 12 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-90921 in the wild and no public exploit code.

Affected product: IBM Maximo AI Service. 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-90921/ (Markdown: https://insights.sbomify.com/CVE-2026-90921/index.md)
```

## Sources

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

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