CVE-2025-0108

CRITICALNVD 9.19.1
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score elevated to 9.1 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2025-02-18), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.1 retained for reference. 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-1505 (ENISA EUVD) · GHSA-hvqq-hwj3-c54m (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
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 low or medium mission impact
CISA-KEV: ExploitedEPSS PROB: 98%CVSS: 9.1Exploit: Public PoCExposed 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 authentication bypass in the Palo Alto Networks PAN-OS software enables an unauthenticated attacker with network access to the management web interface to bypass the authentication otherwise required by the PAN-OS management web interface and invoke certain PHP scripts. While invoking these PHP scripts does not enable remote code execution, it can negatively impact integrity and confidentiality of PAN-OS.

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
9.1
EG Score
9.1CRITICALhigh confidence
EG Risk
96
EG Risk 96/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)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Attend at low or medium mission impact; Act at high (mission-essential systems).
Exploitation active (CISA Vulnrichment) · Automatable yes (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 sooner than your standard update timelines at low or medium mission impact and as soon as possible at high.
EPSS PROB
98%
EPSS %ILE
99th
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.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
98% 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 Attend at medium mission impactAttend at low or medium mission impact; Act at high (mission-essential systems).CISA BOD 26-04: 3 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)Attend at low or medium mission impact; Act at high (mission-essential systems).

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

Exploitation active (CISA Vulnrichment) · Automatable yes (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)3 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 yes (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-0108 · https://nvd.nist.gov/vuln/detail/CVE-2025-0108

Published

February 12, 2025

Last Modified

September 24, 2026

Advisory Details (8)

Auto-updated Nov 2, 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-0108
Web page

Palo Alto warns firewalls flaws are under active attack

https://www.theregister.com/2025/02/19/palo_alto_firewall_attack/
Web page

Palo Alto Networks Confirms Exploitation of Firewall Vulnerability - SecurityWeek

https://www.securityweek.com/palo-alto-networks-confirms-exploitation-of-firewall-vulnerability/
Web page🟡 PoC Available

Palo Alto Networks tags new firewall bug as exploited in attacks

https://www.bleepingcomputer.com/news/security/palo-alto-networks-tags-new-firewall-bug-as-exploited-in-attacks/
Web page

GitHub - iSee857/CVE-2025-0108-PoC: Palo Alto Networks PAN-OS 身份验证绕过漏洞批量检测脚本(CVE-2025-0108) · GitHub

https://github.com/iSee857/CVE-2025-0108-PoC
Web page

CVE-2025-0108 PAN-OS: Authentication Bypass in the Management Web Interface

https://security.paloaltonetworks.com/CVE-2025-0108
Web page

CVE-2025-0108: PAN-OS Auth Bypass via Nginx/Apache Path Confusion

https://slcyber.io/blog/nginx-apache-path-confusion-to-auth-bypass-in-pan-os/

Vendor Advisories for CVE-2025-0108(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 18× in last 7d / 114× 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,000 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 900 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Publicly available exploits

(5 references)

Public exploit code is referenced for this CVE (2 GitHub PoCs), as are 1 Nuclei detection template, 2 GitHub checker repositories. A detection template checks whether a system is affected; it is not necessarily exploit code. A GitHub repository named or described as a checker or scanner checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.

  • Nucleihttp/cves/2025/CVE-2025-0108.yaml
    Published Feb 20, 2025

    PAN-OS Management Interface - Path Confusion to Authentication Bypass

    Open source ↗
  • GitHub checkerbecrevex/CVE-2025-0108
    Published Feb 19, 2025

    NSE script that checks for CVE-2025-0108 vulnerability in Palo Alto Networks PAN-OS

    Open source ↗
  • GitHub checkerfr4nc1stein/CVE-2025-0108-SCAN
    Published Feb 18, 2025

    Detects an authentication bypass vulnerability in Palo Alto PAN-OS (CVE-2025-0108).

    Open source ↗
  • GitHub PoCFOLKS-iwd/CVE-2025-0108-PoC
    Published Feb 14, 2025

    PoC exploit for CVE-2025-0108 - PAN-OS Authentication Bypass

    Open source ↗
  • GitHub PoCiSee857/CVE-2025-0108-PoC
    Published Feb 13, 2025

    Palo Alto Networks PAN-OS 身份验证绕过漏洞批量检测脚本(CVE-2025-0108)

    Open source ↗

Frequently asked(6)

What is CVE-2025-0108?
CVE-2025-0108 is a critical-severity vulnerability; its CVE record was published on February 12, 2025. An authentication bypass in the Palo Alto Networks PAN-OS software enables an unauthenticated attacker with network access to the management web interface to bypass the authentication otherwise required by the PAN-OS management web interface and invoke certain PHP scripts. While invoking these PHP…
When was CVE-2025-0108 made public?
CVE-2025-0108 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 September 24, 2026; the record at its source may have been updated since.
Is CVE-2025-0108 actively exploited?
Yes. CISA added CVE-2025-0108 to the Known Exploited Vulnerabilities catalog on February 18, 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-0108?
CVE-2025-0108 has a CVSS v3 base score of 9.1 (NVD).
Which products are affected by CVE-2025-0108?
CVE-2025-0108 affects Palo Alto Networks PAN-OS.
How do I remediate CVE-2025-0108?
A fix for CVE-2025-0108 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-0108 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2025-0108?

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