# CVE-2025-0111: Palo Alto Networks PAN-OS File Read

> An authenticated attacker can read arbitrary files on the PAN-OS filesystem via the management web interface, exposing sensitive data.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/AU:N/R:U/V:C/RE:M/U:Red`)
- **Exploited in the wild:** Yes, since 20 Feb 2025 (CISA KEV)
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Feb 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-wmcv-pj3g-38rp

## What is CVE-2025-0111?

CVE-2025-0111 is a high-severity path traversal vulnerability in Paloaltonetworks Pan-Os, published on 12 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An authenticated file read vulnerability in the Palo Alto Networks PAN-OS software enables an authenticated attacker with network access to the management web interface to read files on the PAN-OS filesystem that are readable by the “nobody” user.

You can 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  best practices 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 does not affect Cloud NGFW or Prisma Access software.

Weakness: CWE-610 (Externally Controlled Reference to a Resource in Another Sphere), CWE-73 (External Control of File Name or Path)

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

It affects 1 product.


Products: Paloaltonetworks Pan-Os.

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

No fix has been published for CVE-2025-0111 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 13 Mar 2025.

## Is CVE-2025-0111 being exploited?

Yes. Attackers have exploited CVE-2025-0111 in the wild since at least 20 Feb 2025.

## 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-0111 and fix it if it is affected.

What it is: CVE-2025-0111 is a high-severity path traversal vulnerability in Paloaltonetworks Pan-Os, published on 12 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2025-0111 in the wild since at least 20 Feb 2025.

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-0111/ (Markdown: https://insights.sbomify.com/CVE-2025-0111/index.md)
```

## Sources

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

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