# CVE-2025-0124: PAN-OS: Authenticated File Deletion Vulnerability on the Management Web Interface

> Authenticated attackers with management interface access can delete specific logs and configuration files, requiring restricted management access for mitigation.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/AU:N/R:U/V:C/RE:M/U:Amber`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Apr 2025
- **Updated:** 11 Apr 2025
- **Also known as:** GHSA-56hj-453m-vxfv

## What is CVE-2025-0124?

CVE-2025-0124 is a medium-severity path traversal vulnerability in Paloaltonetworks Pan-Os, published on 11 Apr 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An authenticated file deletion vulnerability in the Palo Alto Networks PAN-OS® software enables an authenticated attacker with network access to the management web interface to delete certain files as the “nobody” user; this includes limited logs and configuration files but does not include system files.

The attacker must have network access to the management web interface to exploit this issue. You greatly reduce the risk of this issue by restricting access to the management web interface to only trusted internal IP addresses according to our recommended  critical deployment guidelines https://live.paloaltonetworks.com/t5/community-blogs/tips-amp-tricks-how-to-secure-the-management-access-of-your-palo/ba-p/464431 .

This issue affects Cloud NGFW. However, this issue does not affect Prisma® Access software.

Weakness: CWE-73 (External Control of File Name or Path)

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

It affects 1 product.


Products: Paloaltonetworks Pan-Os.

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

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

## Is CVE-2025-0124 being exploited?

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

## Other vulnerabilities in Paloaltonetworks Pan-Os

- [CVE-2024-3400](https://insights.sbomify.com/CVE-2024-3400/): Palo Alto Networks PAN-OS Command Injection (critical 10.0, exploited in the wild)
- [CVE-2020-2021](https://insights.sbomify.com/CVE-2020-2021/): Palo Alto Networks PAN-OS Authentication Bypass (critical 10.0, exploited in the wild)
- [CVE-2017-15944](https://insights.sbomify.com/CVE-2017-15944/): Palo Alto Networks PAN-OS Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2026-0300](https://insights.sbomify.com/CVE-2026-0300/): Palo Alto Networks PAN-OS Out-of-bounds Write (critical 9.3, exploited in the wild)
- [CVE-2024-0012](https://insights.sbomify.com/CVE-2024-0012/): Palo Alto Networks PAN-OS Management Interface Authentication Bypass (critical 9.3, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-0124 is a medium-severity path traversal vulnerability in Paloaltonetworks Pan-Os, published on 11 Apr 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-0124 in the wild and no public exploit code.

Affected product: Paloaltonetworks Pan-Os. 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-0124/ (Markdown: https://insights.sbomify.com/CVE-2025-0124/index.md)
```

## Sources

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

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