# CVE-2026-14514: Reliable Scalable Cluster Technology Denial-of-Service

> Remote attackers can cause denial of service in IBM RSCT via crafted requests due to improper input validation.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Aug 2026
- **Updated:** 20 Aug 2026
- **Also known as:** GHSA-q5hh-ggj2-4767

## What is CVE-2026-14514?

CVE-2026-14514 is a medium-severity denial of service vulnerability in IBM Reliable Scalable Cluster Technology (RSCT), published on 19 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IBM Reliable Scalable Cluster Technology (RSCT) 3.0 could allow a remote attacker to cause a denial of service by sending a specially crafted request due improper input validation.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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

It affects 1 product.


Products: Ibm Reliable Scalable Cluster Technology.

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

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

## Is CVE-2026-14514 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-14514 is a medium-severity denial of service vulnerability in IBM Reliable Scalable Cluster Technology (RSCT), published on 19 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-14514 in the wild and no public exploit code.

Affected product: IBM Reliable Scalable Cluster Technology (RSCT). 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-14514/ (Markdown: https://insights.sbomify.com/CVE-2026-14514/index.md)
```

## Sources

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

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