# CVE-2025-53636: Open OnDemand Shell App closed websocket DoS

> Attackers can cause a Denial of Service in Open OnDemand by flooding logs through the shell app, requiring an upgrade to mitigate.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L`)
- **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:** 11 Jul 2025
- **Updated:** 14 Jul 2025
- **Also known as:** GHSA-x5xv-fw37-v524

## What is CVE-2025-53636?

CVE-2025-53636 is a medium-severity denial of service vulnerability in OSC ondemand, published on 11 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Open OnDemand is an open-source HPC portal. Users can flood logs by interacting with the shell app and generating many errors. Users who flood logs can create very large log files causing a Denial of Service (DoS) to the ondemand system. This vulnerability is fixed in 3.1.14 and 4.0.6.

Weakness: CWE-779 (Logging of Excessive Data), CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2025-53636?


## How do I fix CVE-2025-53636?

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

## Is CVE-2025-53636 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-53636 and fix it if it is affected.

What it is: CVE-2025-53636 is a medium-severity denial of service vulnerability in OSC ondemand, published on 11 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-53636 in the wild and no public exploit code.

Affected product: OSC ondemand. 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-2025-53636/ (Markdown: https://insights.sbomify.com/CVE-2025-53636/index.md)
```

## Sources

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

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