# CVE-2025-62724: Open OnDemand allowlist bypass using symlinks in directory downloads (TOCTOU)

> Attackers can bypass file allowlists via symlink TOCTOU race conditions to read unauthorized files in Open OnDemand HPC portals.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A: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:** 20 Nov 2025
- **Updated:** 21 Nov 2025
- **Also known as:** GHSA-vjpg-34px-gjrw

## What is CVE-2025-62724?

CVE-2025-62724 is a medium-severity path traversal vulnerability in OSC ondemand, published on 20 Nov 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. Prior to versions 4.0.8 and 3.1.16, users can craft a "Time of Check to Time of Use" (TOCTOU) attack when downloading zip files to access files outside of the OOD_ALLOWLIST. This vulnerability impacts sites that use the file browser allowlists in all current versions of OOD. However, files accessed are still protected by the UNIX permissions. Open OnDemand versions 4.0.8 and 3.1.16 have been patched for this vulnerability.

Weakness: CWE-61 (UNIX Symbolic Link (Symlink) Following), CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

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


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

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

## Is CVE-2025-62724 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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