CVE-2025-0111
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.
do firstApply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? No. The attack requires authentication and network access to the management web interface, and the malicious request looks like a normal authenticated file read request without unusual patterns that a WAF could reliably detect.
Also consider: patch
Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2025-0111 being exploited?
Yes. CVE-2025-0111 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2025-0111?
CVE-2025-0111 is rated Medium with a CVSS score of 6.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-0111?
Yes. A fix has been recorded for CVE-2025-0111. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-0111 affect?
CVE-2025-0111 affects paloaltonetworks:pan-os. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected>= 10.1.0 and < 10.1.14-h9
- affected>= 10.2.0 and < 10.2.7-h24
- affected>= 11.1.0 and < 11.1.6-h1
- affected>= 11.2.0 and < 11.2.4-h4
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
cisa ssvc
- exploitation
- active
- automatable
- no
- technical impact
- partial
Assessed by CISA 21 Feb 2025 (SSVC 2.0.3).
timeline
- 12 Feb 2025Published
- 20 Feb 2025Added to CISA KEV (exploited in the wild) · 7 days later
- 21 Feb 2025CISA SSVC assessment: exploitation active · 1 day later
- 13 Mar 2025CISA remediation due date (US federal agencies) · 20 days later
- 26 Feb 2026CVE record last updated · 351 days (about 12 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 249 days (about 8 months) later
- Advisorysecurity.paloaltonetworks.com /CVE-2025-0111
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-0111
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.