CriticalCVE-2025-0111

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

    Published In CISA KEV since Sources: pwn.watch, CVE.org

    What is affected, what to do

    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 .

    The vulnerability is being actively exploited; treat it as a priority. Update Palo Alto Networks PAN-OS to version 10.1.14-h9, Palo Alto Networks PAN-OS to version 10.2.7-h24, Palo Alto Networks PAN-OS to version 11.1.6-h1. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • Palo Alto Networks PAN-OS lt 10.1.0..10.1.14-h9
    • Palo Alto Networks PAN-OS lt 10.2.0..10.2.7-h24
    • Palo Alto Networks PAN-OS lt 11.1.0..11.1.6-h1
    • Palo Alto Networks PAN-OS lt 11.2.0..11.2.4-h4
    Fixed in
    • Palo Alto Networks PAN-OS 10.1.14-h9
    • Palo Alto Networks PAN-OS 10.2.7-h24
    • Palo Alto Networks PAN-OS 11.1.6-h1
    • Palo Alto Networks PAN-OS 11.2.4-h4

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    7.1

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v4

    6.5

    CVSS v3

    Severity Medium on the scale from 0 to 10.

    Source: pwn.watch, CVE.org

    2.0 %

    EPSS score

    Moderate — model estimates 1-10% exploitation likelihood.

    Source: FIRST EPSS, percentile 80.6

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    195.38 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploitedSource: VulnCheck KEV (opens in a new tab) How we classify
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    7.1 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    6.5
    CVSS v4

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    7.1
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    2.0 %
    Moderate — model estimates 1-10% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    80.6
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-73

    Response and mitigation

    Why act now?

    Prioritisation rationale

    On its own the flaw looks moderate: it requires network reach to the management interface plus a valid login, and its impact is limited to confidentiality. It earned its KEV listing because attackers chain it with the CVE-2025-0108 authentication bypass, which together allow unauthenticated file reads on exposed firewalls. Attackers typically use this to harvest configuration data and credentials as a foothold for further intrusion. CISA reports no known ransomware use, but exploitation likelihood is clearly elevated. If your management interface is reachable from the internet or from user networks, treat this as critical and remediate within 24 h. If management is strictly out-of-band and isolated, the next regular maintenance window is acceptable.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Check and lock down management web interface exposure: In Device > Setup > Interfaces > Management (Permitted IP Addresses) and in every Interface Management Profile (Network > Network Profiles), disable HTTPS/HTTP on dataplane interfaces or restrict them to dedicated admin jump hosts. Internet-facing management interfaces come first.
      • Patch: Upgrade to the fixed releases 11.2.4-h4, 11.1.6-h1, 10.2.7-h24 or 10.1.14-h9, or later. Other 10.2.x maintenance trains have their own hotfix levels, so look up the exact version in the vendor advisory. Move 11.0.x devices to a supported train. Cloud NGFW and Prisma Access are not affected.
      • Account for chaining: Public reporting documents this CVE being combined with the authentication bypass CVE-2025-0108 (and CVE-2024-9474), which effectively removes the "authenticated" precondition. Patch both in the same maintenance window.
      • Compromise assessment for exposed devices: If a device was reachable from untrusted networks, capture a tech support file for evidence before rebooting. Then rotate admin passwords, API keys, and any locally stored certificates or secrets that the "nobody" user could have read.
      • Clean up admin accounts: Disable unknown or stale administrator accounts and trim roles with web UI access to the minimum. Any valid low-privilege login is enough to exploit this flaw.
    2. Runbook step 2

      Mitigation layers

      • Network segmentation: Place the management interface exclusively in an out-of-band management VLAN. Allow access only from a PAW/jump-host zone, and drop TCP/443 and TCP/4443 to the management IP from all other zones on upstream firewalls/ACLs.
      • IPS/Threat Prevention: Install the latest content update containing the Threat Prevention signatures for CVE-2025-0108/CVE-2025-0111 (per advisory). Where management is reached through interface management profiles, route that traffic through a security policy with a Vulnerability Protection profile attached.
      • Upstream WAF/proxy rule: Block requests to the management interface that contain encoded traversal sequences (%2e%2e, %252e, ..%2f) or that hit /unauth/ paths and then reach into /php/.
      • IAM/least privilege: Enforce admin authentication through a central IdP with MFA (SAML/RADIUS). Keep local accounts for break-glass use only and shorten admin session timeouts.
      • Configuration hardening: Do not host GlobalProtect portals or gateways on interfaces that also carry a management profile. Disable Telnet/HTTP globally and validate the result against Palo Alto's "Best Practices for Securing Administrative Access".
    3. Runbook step 3

      Detection rules

      • Management web server logs (tech support file or syslog forwarding): Hunt for double-encoded traversal in URIs, e.g. SPL: index=panos sourcetype=pan:* (uri="*%252e%252e*" OR uri="*/unauth/*/php/*").
      • Network telemetry (Zeek/Suricata): Alert on HTTP(S) sessions to the management IP from sources outside the admin zone. Zeek approach: conn.log where id.resp_h in mgmt_ips and id.resp_p in {443,4443} and not id.orig_h in admin_nets.
      • PAN-OS system/config logs: Review admin logins from unknown source IPs or at unusual hours, as well as failed logins followed by a success. A Sigma rule with logsource: product: paloalto, service: system should match eventid: auth-success and negate a source-IP allowlist.
      • Threat log: Treat any hit on the Threat Prevention signatures for CVE-2025-0108/0111 as a confirmed exploitation attempt. KQL (CommonSecurityLog): CommonSecurityLog | where DeviceVendor=="Palo Alto Networks" and Activity=="THREAT" and Message has_any ("CVE-2025-0108","CVE-2025-0111").
      • Follow-on activity: Correlate config commits, new admin accounts, or API key generation that occur shortly after suspicious management-plane access.

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    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.

    Source: pwn.watch, NVD (NIST), cvelistv5, CISA KEV Catalog, CVE.org (MITRE)

    Vendors and products

    Affected operating systems

    Affected operating systems
    Otherpaloaltonetworkspan-os10.1.0
    Otherpaloaltonetworkspan-os10.1.1
    Otherpaloaltonetworkspan-os10.1.10
    Otherpaloaltonetworkspan-os10.1.11
    Otherpaloaltonetworkspan-os10.1.12
    Otherpaloaltonetworkspan-os10.1.13
    Otherpaloaltonetworkspan-os10.1.14
    Otherpaloaltonetworkspan-os10.1.2
    Otherpaloaltonetworkspan-os10.1.3
    Otherpaloaltonetworkspan-os10.1.4
    Otherpaloaltonetworkspan-os10.1.5
    Otherpaloaltonetworkspan-os10.1.6
    Otherpaloaltonetworkspan-os10.1.7
    Otherpaloaltonetworkspan-os10.1.8
    Otherpaloaltonetworkspan-os10.1.9
    Otherpaloaltonetworkspan-os10.2.0
    Otherpaloaltonetworkspan-os10.2.1
    Otherpaloaltonetworkspan-os10.2.10
    Otherpaloaltonetworkspan-os10.2.11
    Otherpaloaltonetworkspan-os10.2.12
    Otherpaloaltonetworkspan-os10.2.13
    Otherpaloaltonetworkspan-os10.2.2
    Otherpaloaltonetworkspan-os10.2.3
    Otherpaloaltonetworkspan-os10.2.4

    Weakness classes (CWE)

    • CWE-73External Control of File Name or Path

      Base

      The product allows user input to control or influence paths or file names that are used in filesystem operations.

      Entry at MITRE CWE-73

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited

    References & sources

    • security.paloaltonetworks.comPalo Alto Networks advisory: Palo Alto Networks PAN-OSVendor advisory, Vendor advisory, pwn-watch
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2025-0111government-resource, US government resource
    • pwn.watchpwn.watch: Palo Alto Networks PAN-OS: PAN-OS File Read Vulnerabilitypwn-watch
    • NVD (NIST)NVD: CVE-2025-0111pwn-watch
    • cisa.govCISA Known Exploited Vulnerabilities Catalogpwn-watch
    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2025-0111
    <a href="https://intel.neosec.eu/en/cve/CVE-2025-0111"><img src="https://intel.neosec.eu/badge/cve/CVE-2025-0111.svg?lang=en" alt="CVE-2025-0111 – NEOSEC Intel" height="20"></a>