dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 11 Mar 2025.
Pan OsOperating system · Paloaltonetworks

CVE-2025-0108

CRITICAL · 9.1 CVSS v3.1 Published 2025-02-12
Fix available
A fix is available. Upgrade to 10.1.14 / 10.2.7 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Palo Alto Networks PAN-OS contains an authentication bypass vulnerability in its management web interface. An unauthenticated attacker with network access can bypass authentication and invoke certain PHP scripts, impacting integrity and confidentiality without enabling remote code execution.

MitigationRestrict access to the PAN-OS management web interface to only trusted internal IP addresses per Palo Alto best practices guidelines.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Pan OsOperating system
Affected:>= 10.1.0, < 10.1.14>= 10.2.0, < 10.2.7>= 11.1.0, < 11.1.2>= 11.2.0, < 11.2.4= 10.1.14= 10.2.7= 10.2.8= 10.2.9= 10.2.10= 10.2.11= 10.2.12= 10.2.13

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check PAN-OS version
    Use the command 'show system info' or access the web interface to view the software version. Compare your installed version against the affected ranges: 10.1.0 to 10.1.13, 10.2.0 to 10.2.6, 11.1.0 to 11.1.1, 11.2.0 to 11.2.3, and the specific versions 10.1.14, 10.2.7 through 10.2.13
    Affected if Your PAN-OS version falls within any of the affected version ranges listed
  2. Verify management interface exposure
    Review your network configuration to determine if the PAN-OS management web interface (typically ports 443 or 8080) is accessible from untrusted or external networks. Check firewall rules, interface bindings, and service listener configurations.
    Affected if The management web interface is reachable from networks that are not trusted internal IP addresses
  3. Check interface binding configuration
    Execute 'show management interface' or review the management interface settings to identify which IP addresses and interfaces the web management service is listening on.
    Affected if The management interface is bound to any interface other than a dedicated internal management-only interface
  4. Review access restrictions on management services
    Examine the management service access list using 'show config system management' or similar commands to confirm whether source IP restrictions are configured and enforced.
    Affected if No source IP allowlist is configured or the allowlist includes untrusted/external IP ranges

You are affected if your PAN-OS version is in the vulnerable list AND the management web interface is accessible from untrusted networks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.1.14 / 10.2.7 / 11.1.2 or later
Fixed in 10.1.1410.2.711.1.2
Interim mitigation

Restrict access to the PAN-OS management web interface to only trusted internal IP addresses per Palo Alto best practices guidelines.

Recommended fix High confidence

Upgrade to PAN-OS 10.1.14, 10.2.7, 11.1.2, or 11.2.4 (choose the appropriate version based on your current branch)

  1. 1. Identify the current PAN-OS version by navigating to Device > Setup > Operations or checking the dashboard.
  2. 2. Determine which version branch you are currently on (10.1.x, 10.2.x, 11.1.x, or 11.2.x).
  3. 3. Download the appropriate fixed version from the Palo Alto Networks support portal: 10.1.14 for 10.1.x, 10.2.7 for 10.2.x, 11.1.2 for 11.1.x, or 11.2.4 for 11.2.x.
  4. 4. Review the release notes for the target version to verify compatibility with your hardware/model and connected Panorama appliances.
  5. 5. Before upgrading, back up the current configuration via Device > Setup > Operations > Save Device State.
  6. 6. Upload and install the upgrade via Device > Software > Upload or via the CLI using 'request system software install <filename>'
  7. 7. After installation, reboot the device and verify the new version under Device > Setup > Operations.
  8. 8. As an additional layered defense, restrict management interface access to trusted internal IPs only via Network > Interfaces > Management > Access Domain or CLI: 'set deviceconfig system mgmt-interface-allow-list <trusted-ips>'.
Caveat Review release notes for potential changes to feature behavior, API compatibility, or hardware support before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pan Os Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0108 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-0108 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data