# CVE-2026-50589: OpenStack Ironic: Crafted JSON String to Certain Endpoints on the API or JSON-RPC Service May Result in Service Crash

> Unauthenticated attackers can crash OpenStack Ironic services by submitting crafted JSON strings to API or JSON-RPC endpoints.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Jun 2026
- **Updated:** 16 Jul 2026
- **Also known as:** DEBIAN-CVE-2026-50589, GHSA-q3g8-rjrx-59ph, PYSEC-2026-216, UBUNTU-CVE-2026-50589

## What is CVE-2026-50589?

CVE-2026-50589 is a medium-severity unsafe deserialization vulnerability in OpenStack Ironic, published on 4 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In OpenStack Ironic 32 before 37.0.0, an unauthenticated malicious user could submit a crafted JSON string to some endpoints on the API or JSON-RPC service and effect a service crash.

Weakness: CWE-502 (Deserialization of Untrusted Data), CWE-770 (Allocation of Resources Without Limits or Throttling)

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

3 open source packages ship an affected version, including ironic. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ironic` | PyPI | From 32.0.0 | 37.0.0 |
| `ironic` | PyPI | From 32.0.0 | 37.0.0 |
| `ironic` | PyPI | From 32.0.0 | 37.0.0 |

Products: Openstack Ironic.

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

Upgrade ironic to 37.0.0 or later.

## Is CVE-2026-50589 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-50589 exists.

## Other vulnerabilities in OpenStack Ironic

- [CVE-2026-42997](https://insights.sbomify.com/CVE-2026-42997/): OpenStack Ironic has an Incorrect Resource Transfer Between Spheres (high 7.7)
- [CVE-2026-42510](https://insights.sbomify.com/CVE-2026-42510/): OpenStack Ironic is Vulnerable to Inclusion of Functionality from Untrusted Control Sphere (medium 6.6)
- [CVE-2015-7514](https://insights.sbomify.com/CVE-2015-7514/): Information disclosure in n/a (medium 6.5)
- [CVE-2026-48681](https://insights.sbomify.com/CVE-2026-48681/): OpenStack Ironic allows file overwrite via directory traversal during deployment with a crafted ISO image (medium 5.9)
- [CVE-2026-46447](https://insights.sbomify.com/CVE-2026-46447/): OpenStack Ironic allows Boot Script Injection (medium 5.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-50589 is a medium-severity unsafe deserialization vulnerability in OpenStack Ironic, published on 4 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-50589 exists.

Affected packages and fixed versions:
- ironic (PyPI): affected from 32.0.0; fixed in 37.0.0
- ironic (PyPI): affected from 32.0.0; fixed in 37.0.0
- ironic (PyPI): affected from 32.0.0; fixed in 37.0.0

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

## Sources

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

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