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

CVE-2025-0111

MEDIUM · 6.5 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 Remotely reachable 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 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.

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

This is an authenticated file read vulnerability in PAN-OS management web interface. An attacker with valid credentials and network access to the management interface can read files on the filesystem that are readable by the 'nobody' user, potentially exposing sensitive configuration files or system data.

MitigationRestrict access to the PAN-OS management web interface to only trusted internal IP addresses following Palo Alto Networks best practices for securing management access.

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>= 10.2.10, < 10.2.12>= 11.0.0, < 11.1.6>= 11.2.0, < 11.2.4= 10.1.14= 10.2.7= 10.2.8= 10.2.9= 10.2.12= 10.2.13= 11.1.6

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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
    Run 'show system info' or 'request system software-info' from the PAN-OS CLI to obtain the installed software version.
    Affected if The installed version falls within any of these ranges: 10.1.0 through 10.1.14 (excluding 10.1.14-h2 and later), 10.2.0 through 10.2.13 (excluding 10.2.14+), 11.0.0 through 11.1.6 (excluding 11.1.7+), or 11.2.0 through 11.2.4 (excluding 11.2.5+). Compare your version against these affected ranges.
  2. Verify management web interface is enabled
    Run 'show management interface' or check the Management > Setup > Management Interface settings in the web UI to confirm the management web interface (HTTPS) is enabled.
    Affected if The management web interface is enabled and accessible.
  3. Check network accessibility of management interface
    Review firewall or ACL rules to determine whether the PAN-OS management interface (port 443) is reachable from untrusted networks or external IP addresses.
    Affected if The management web interface is exposed to networks beyond trusted internal IPs, allowing authenticated attackers network access.
  4. Identify valid administrator accounts
    Run 'show admins' from CLI or review the Device > Administrators list in the web UI to see configured administrative users.
    Affected if Valid administrative credentials exist, which an attacker could use to exploit this vulnerability if they gain network access to the management interface.

You are affected if your PAN-OS version is within the affected ranges AND the management web interface is enabled and accessible to the attacker (whether directly or through compromised credentials on a reachable network).

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 / 10.2.12 or later
Fixed in 10.1.1410.2.710.2.12
Interim mitigation

Restrict access to the PAN-OS management web interface to only trusted internal IP addresses following Palo Alto Networks best practices for securing management access.

Recommended fix High confidence

10.1.14, 10.2.7, 10.2.12, or 11.1.6 depending on current branch (10.1.x, 10.2.0-10.2.6, 10.2.10-10.2.11, or 11.0.x respectively)

  1. Identify the current PAN-OS version running on the device
  2. Determine the appropriate upgrade path based on current version: for 10.1.x upgrade to 10.1.14, for 10.2.0-10.2.6 upgrade to 10.2.7, for 10.2.10-10.2.11 upgrade to 10.2.12, for 11.0.x upgrade to 11.1.6
  3. Review Palo Alto Networks upgrade guide and release notes for the target version
  4. Download the appropriate PAN-OS update from the Palo Alto Networks support portal
  5. Schedule a maintenance window considering upgrade time and potential downtime
  6. Perform a backup of the device configuration
  7. Upgrade the PAN-OS software to the fixed version
  8. Verify the upgrade was successful and the device is functioning properly
Caveat Standard PAN-OS upgrade considerations apply - review release notes for behavioral changes and ensure compatibility with Panorama and connected devices

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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-0111 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