CVE-2025-0111

CRITICALNVD 6.59.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2025-02-20), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 6.5 retained for reference. The 9.0 is the floor for confirmed exploitation, not an impact rating: this CVE's impact severity (EG Severity) is CVSS 6.5 MEDIUM under GitHub Security Advisory CVSS. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekExploited in the wild

Also known asEUVD-2025-1508 (ENISA EUVD) · GHSA-wmcv-pj3g-38rp (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at every mission impact level
CISA-KEV: ExploitedEPSS PROB: 2.0%CVSS: 6.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Fixed versions, as the CVE record's CNA (Palo Alto Networks, Inc.) states them: "Upgrade to 10.1.14-h9 or later".

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.

CVSS v3
6.5
EG Score
9.0CRITICALhigh confidence
EG Risk
69
EG Risk 69/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
2.0%
EPSS %ILE
80th
KEV
⚠ Exploited

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is the CISA KEV floor for confirmed exploitation, not an impact rating: its impact severity (EG Severity) is CVSS 6.5 MEDIUM.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
2.0% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
CISA KEV and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 14 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 14 days if it is not.

The score's inputs: In CISA KEV yes (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

CISA required action“Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://security.paloaltonetworks.com/CVE-2025-0111 · https://nvd.nist.gov/vuln/detail/CVE-2025-0111

Published

February 12, 2025

Last Modified

November 4, 2025

Advisory Details (2)

Auto-updated Oct 27, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). Patch available. Sources: cisa.
CISA🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-0111
Web page

CVE-2025-0111 PAN-OS: Authenticated File Read Vulnerability in the Management Web Interface

https://security.paloaltonetworks.com/CVE-2025-0111

Vendor Advisories for CVE-2025-0111(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 21× in last 7d / 135× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 1,128 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 1,028 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 00:59 UTCEG score recompute
  2. 2026-11-02 00:59 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  3. 2026-11-01 16:32 UTCEPSS rescoreEPSS 2.0% · 80th percentile
  4. 2026-11-01 01:16 UTCEG score recompute
  5. 2026-11-01 01:16 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  6. 2026-10-31 16:30 UTCEPSS rescoreEPSS 2.0% · 80th percentile
  7. 2026-10-31 01:32 UTCEG score recompute
  8. 2026-10-31 01:32 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  9. 2026-10-30 16:32 UTCEPSS rescoreEPSS 2.0% · 80th percentile
  10. 2026-10-30 01:48 UTCEG score recompute
  11. 2026-10-30 01:48 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  12. 2026-10-29 16:31 UTCEPSS rescoreEPSS 2.0% · 80th percentile
  13. 2026-10-29 02:05 UTCEG score recompute
  14. 2026-10-29 02:05 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  15. 2026-10-28 16:30 UTCEPSS rescoreEPSS 2.0% · 80th percentile
  16. 2026-10-28 02:22 UTCEG score recompute
  17. 2026-10-28 02:22 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  18. 2026-10-27 16:30 UTCEPSS rescoreEPSS 2.0% · 80th percentile
  19. 2026-10-27 02:39 UTCEG score recompute
  20. 2026-10-27 02:38 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  21. 2026-10-26 16:29 UTCEPSS rescoreEPSS 2.0% · 80th percentile
  22. 2026-10-26 02:53 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  23. 2026-10-25 16:50 UTCEG score recompute
  24. 2026-10-25 16:30 UTCEPSS rescoreEPSS 2.0% · 80th percentile
  25. 2026-10-25 03:10 UTCEG score recompute
Show 75 more
  1. 2026-10-25 03:10 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  2. 2026-10-24 16:30 UTCEPSS rescoreEPSS 2.0% · 80th percentile
  3. 2026-10-24 03:27 UTCEG score recompute
  4. 2026-10-24 03:27 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  5. 2026-10-23 16:30 UTCEPSS rescoreEPSS 2.0% · 80th percentile
  6. 2026-10-23 03:43 UTCEG score recompute
  7. 2026-10-23 03:43 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  8. 2026-10-22 16:32 UTCEPSS rescoreEPSS 2.0% · 80th percentile
  9. 2026-10-22 03:58 UTCEG score recompute
  10. 2026-10-22 03:58 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  11. 2026-10-21 16:30 UTCEPSS rescoreEPSS 2.0% · 80th percentile
  12. 2026-10-21 04:14 UTCEG score recompute
  13. 2026-10-21 04:14 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  14. 2026-10-20 16:31 UTCEPSS rescoreEPSS 2.0% · 80th percentile
  15. 2026-10-20 04:31 UTCEG score recompute
  16. 2026-10-20 04:31 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  17. 2026-10-19 16:30 UTCEPSS rescoreEPSS 2.0% · 80th percentile
  18. 2026-10-19 04:46 UTCEG score recompute
  19. 2026-10-19 04:46 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  20. 2026-10-18 16:30 UTCEPSS rescoreEPSS 2.0% · 80th percentile
  21. 2026-10-18 05:01 UTCEG score recompute
  22. 2026-10-18 05:01 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  23. 2026-10-17 16:32 UTCEPSS rescoreEPSS 2.0% · 80th percentile
  24. 2026-10-17 05:18 UTCEG score recompute
  25. 2026-10-17 05:18 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  26. 2026-10-16 16:37 UTCEPSS rescoreEPSS 2.0% · 80th percentile
  27. 2026-10-16 05:35 UTCEG score recompute
  28. 2026-10-16 05:35 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  29. 2026-10-15 16:30 UTCEPSS rescoreEPSS 2.0% · 80th percentile
  30. 2026-10-15 05:52 UTCEG score recompute
  31. 2026-10-15 05:52 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  32. 2026-10-14 16:30 UTCEPSS rescoreEPSS 2.0% · 80th percentile
  33. 2026-10-14 06:09 UTCEG score recompute
  34. 2026-10-14 06:09 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  35. 2026-10-13 16:31 UTCEPSS rescoreEPSS 2.0% · 80th percentile
  36. 2026-10-13 06:24 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  37. 2026-10-12 17:28 UTCEG score recompute
  38. 2026-10-12 16:32 UTCEPSS rescoreEPSS 2.0% · 80th percentile
  39. 2026-10-12 06:40 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  40. 2026-10-12 02:30 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  41. 2026-10-11 22:23 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  42. 2026-10-11 20:58 UTCEG score recompute
  43. 2026-10-11 18:16 UTCEG score recompute
  44. 2026-10-11 18:16 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  45. 2026-10-11 14:07 UTCEG score recompute
  46. 2026-10-11 14:07 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  47. 2026-10-11 13:46 UTCEPSS rescoreEPSS 2.0% · 80th percentile
  48. 2026-10-11 09:59 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  49. 2026-10-11 05:51 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  50. 2026-10-11 01:43 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  51. 2026-10-10 21:34 UTCEG score recompute
  52. 2026-10-10 21:34 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  53. 2026-10-10 19:58 UTCEPSS rescoreEPSS 2.0% · 80th percentile
  54. 2026-10-10 17:25 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  55. 2026-10-10 13:18 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  56. 2026-10-10 09:10 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  57. 2026-10-10 05:02 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  58. 2026-10-10 00:55 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  59. 2026-10-09 20:47 UTCEG score recompute
  60. 2026-10-09 20:47 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  61. 2026-10-09 20:06 UTCEPSS rescoreEPSS 2.0% · 80th percentile
  62. 2026-10-09 16:40 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  63. 2026-10-09 12:33 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  64. 2026-10-09 08:25 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  65. 2026-10-09 04:17 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  66. 2026-10-09 00:10 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  67. 2026-10-08 20:03 UTCEG score recompute
  68. 2026-10-08 20:03 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  69. 2026-10-08 17:08 UTCEPSS rescoreEPSS 2.0% · 80th percentile
  70. 2026-10-08 15:56 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  71. 2026-10-08 11:48 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  72. 2026-10-08 07:41 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  73. 2026-10-08 03:34 UTCEG score recompute
  74. 2026-10-08 03:34 UTCGHSA enrichmentGHSA-wmcv-pj3g-38rp · GitHub severity HIGH · GitHub CVSS 6.5
  75. 2026-10-07 23:46 UTCEPSS rescoreEPSS 2.0% · 80th percentile

Frequently asked(6)

What is CVE-2025-0111?
CVE-2025-0111 is a critical-severity vulnerability; its CVE record was published on February 12, 2025. 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…
When was CVE-2025-0111 made public?
CVE-2025-0111 was made public on February 12, 2025: that is the date its CVE record's CNA, Palo Alto Networks, Inc., gives for when the vulnerability was made public. The CVE record itself was published on February 12, 2025. EchelonGraph's copy of the record carries a last-modified date of November 4, 2025; the record at its source may have been updated since.
Is CVE-2025-0111 actively exploited?
Yes. CISA added CVE-2025-0111 to the Known Exploited Vulnerabilities catalog on February 20, 2025, affecting Palo Alto Networks PAN-OS. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2025-0111?
CVE-2025-0111 has a CVSS v3 base score of 6.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
Which products are affected by CVE-2025-0111?
CVE-2025-0111 affects Palo Alto Networks PAN-OS.
How do I remediate CVE-2025-0111?
A fix for CVE-2025-0111 is available: update to the fixed version the vendor names in its advisory. Fixed versions, as the CVE record's CNA (Palo Alto Networks, Inc.) states them: "Upgrade to 10.1.14-h9 or later". The vendor advisories EchelonGraph has for CVE-2025-0111 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-0111

Explore →

Is Your Infrastructure Affected by CVE-2025-0111?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.