# CVE-2026-22598: ManageIQ vulnerable to DoS Attack when creating TimeProfiles

> Attackers can cause denial of service in ManageIQ by creating malformed TimeProfiles, leading to timeouts in UI and API requests.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jan 2026
- **Updated:** 21 Jan 2026
- **Also known as:** GHSA-m832-x3g8-63j3

## What is CVE-2026-22598?

CVE-2026-22598 is a high-severity denial of service vulnerability in manageiq, published on 21 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ManageIQ is an open-source management platform. A flaw was found in the ManageIQ API prior to version radjabov-2 where a malformed TimeProfile could be created causing later UI and API requests to timeout leading to a Denial of Service. Version radjabov-2 contains a patch. One may also apply the patch manually.

Weakness: CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2026-22598 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-22598 is a high-severity denial of service vulnerability in manageiq, published on 21 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-22598 in the wild and no public exploit code.

Affected product: manageiq. 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-22598/ (Markdown: https://insights.sbomify.com/CVE-2026-22598/index.md)
```

## Sources

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

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