Skip to content
vulnerability

CVE-2025-0108

9.1
Critical
KEV · Exploited in wildEPSS 98%Patch available

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.

exploited
Yes, in CISA KEV since 18 Feb 2025fix by 11 Mar 2025 (CISA deadline for US federal agencies)unvetted proof-of-concept code on github
fix
Patch available see the advisory in the references
likelihood
EPSS 98.5%
Published 12 Feb 2025Analysed here 2 Nov 2026

do firstApply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

triage
server-sideruntimeWAF can block: partlyAV · networkCWE-306· Missing Authentication

Can a WAF block it? Partly. Cloudflare publishes WAF a rule written for this CVE. Such rules block the known exploit requests and buy time, but attackers can change the request to get past them, so they do not replace the patch.

Also consider: patch · enable the vendor rule in block mode

Based on WAF vendor rules published for this CVE. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

cvss vector
attack vectornetworkattack complexitylowprivileges requirednoneuser interactionnonescopeunchangedconfidentialityhighintegrityhighavailabilitynone
CVSS 3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
common questions

Is CVE-2025-0108 being exploited?

Yes. CVE-2025-0108 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-0108?

CVE-2025-0108 is rated Critical with a CVSS score of 9.1. 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-0108?

Yes. A fix has been recorded for CVE-2025-0108. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2025-0108 affect?

CVE-2025-0108 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.

executive summary
technical analysis
affected
paloaltonetworks:pan-os
affected versions
Palo Alto Networks PAN-OS
  • 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.

public exploits

Unvetted proof-of-concept code on GitHub: 7 GitHub proofs of concept · 1 Nuclei template

GitHub proofs of concept
+3 more repositories

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

cisa ssvc

exploitation
active
automatable
yes
technical impact
partial

Assessed by CISA 19 Feb 2025 (SSVC 2.0.3).

timeline

  1. 12 Feb 2025Published
  2. 13 Feb 2025First proof-of-concept repository on GitHub (unvetted) · same day later
  3. 18 Feb 2025Added to CISA KEV (exploited in the wild) · 5 days later
  4. 19 Feb 2025CISA SSVC assessment: exploitation active · 1 day later
  5. 11 Mar 2025CISA remediation due date (US federal agencies) · 20 days later
  6. 26 Feb 2026CVE record last updated · 353 days (about 12 months) later
  7. 2 Nov 2026Analysed by vulneraibility.com · 249 days (about 8 months) later
how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
NVDCVE.orgCVE DetailsSource
8 references in the CVE record: 1 advisory, 7 links

sources

get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved