# CVE-2024-9363: Unauthorized File Deletion in polyaxon/polyaxon

> An attacker can delete critical files in Polyaxon containers without authentication, causing denial of service by terminating API services.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Mar 2025
- **Updated:** 20 Mar 2025
- **Also known as:** GHSA-m47g-ghr5-3734

## What is CVE-2024-9363?

CVE-2024-9363 is a high-severity path traversal vulnerability in polyaxon/polyaxon, published on 20 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An unauthorized file deletion vulnerability exists in the latest version of the Polyaxon platform, which can lead to denial of service by terminating critical containers. An attacker can delete important files within the containers, such as `polyaxon.sock`, causing the API container to exit unexpectedly. This disrupts related services and prevents the system from functioning normally, without requiring authentication or UUID parameters.

Weakness: CWE-23 (Relative Path Traversal)

## Which versions are affected by CVE-2024-9363?


## How do I fix CVE-2024-9363?

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

## Is CVE-2024-9363 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-9363 and fix it if it is affected.

What it is: CVE-2024-9363 is a high-severity path traversal vulnerability in polyaxon/polyaxon, published on 20 Mar 2025. 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-2024-9363 exists.

Affected product: polyaxon/polyaxon. 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-2024-9363/ (Markdown: https://insights.sbomify.com/CVE-2024-9363/index.md)
```

## Sources

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

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