# CVE-2025-64185: Open OnDemand RPM packages create world writable locations

> Open OnDemand creates world-writable GEM_PATH locations, allowing local attackers to inject code or escalate privileges.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Nov 2025
- **Updated:** 21 Nov 2025
- **Also known as:** GHSA-r2cg-hg78-gq9p

## What is CVE-2025-64185?

CVE-2025-64185 is a medium-severity vulnerability in OSC ondemand, published on 20 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Open OnDemand is an open-source HPC portal. Prior to versions 4.0.8 and 3.1.16, Open OnDemand packages create world writable locations in the GEM_PATH. Open OnDemand versions 4.0.8 and 3.1.16 have been patched for this vulnerability.

Weakness: CWE-552 (Files or Directories Accessible to External Parties), CWE-277 (Insecure Inherited Permissions)

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


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

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

## Is CVE-2025-64185 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-64185 is a medium-severity vulnerability in OSC ondemand, published on 20 Nov 2025. 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-2025-64185 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-64185/ (Markdown: https://insights.sbomify.com/CVE-2025-64185/index.md)
```

## Sources

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

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