dbcve.org
Pan OsOperating system · Paloaltonetworks

CVE-2026-0259

HIGH · 8.8 CVSS v3.1 Published 2026-05-13
Fix available
A fix is available. Upgrade to 10.2.7 / 10.2.10 or later.
See remediation →
94/100
Remediation priority · Urgent
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 arbitrary File Read and Delete Vulnerability in Palo Alto Networks WildFire® WF-500 and WF-500-B appliances enables users to read sensitive information and delete arbitrary files. This vulnerability affects WF-500 and WF-500-B appliances running in the default non-FIPS configuration mode. The WildFire Appliance (WF-500, WF-500-B) software update is now available to customers that use the WildFire Appliance (WF-500, WF-500-B) for on-premise sandboxing. Please note that customers using the WildFire Public cloud service are NOT impacted by this vulnerability.

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

Arbitrary file read and delete vulnerability in Palo Alto Networks WildFire WF-500 and WF-500-B appliances running in non-FIPS mode allows authenticated users to read sensitive information and delete arbitrary files on the filesystem.

MitigationApply the WildFire Appliance software update released by Palo Alto Networks to remediate this vulnerability in affected WF-500 and WF-500-B appliances.

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.2.7>= 10.2.8, < 10.2.10>= 10.2.11, < 10.2.13>= 10.2.14, < 10.2.16= 10.2.7= 10.2.10= 10.2.13= 10.2.16= 10.2.17= 10.2.18>= 11.1.0, < 11.1.4>= 11.1.5, < 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
High
Availability
High

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

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. Confirm WildFire appliance model
    Identify if the device is a Palo Alto Networks WildFire WF-500 or WF-500-B appliance. Check the hardware model or product documentation.
    Affected if Device is not a WF-500 or WF-500-B appliance, then it is not affected by this specific vulnerability.
  2. Check PAN-OS version
    Run 'show system info' or access the device dashboard to retrieve the installed PAN-OS version.
    Affected if Version matches any of these ranges: < 10.2.7; >= 10.2.8, < 10.2.10; >= 10.2.11, < 10.2.13; >= 10.2.14, < 10.2.16; = 10.2.7; = 10.2.10; = 10.2.13; = 10.2.16; = 10.2.17; = 10.2.18; >= 11.1.0, < 11.1.4; >= 11.1.5, < 11.1.6.
  3. Verify FIPS configuration mode
    Check the device configuration for FIPS mode status. Access the web interface under Device > Setup > Management or use CLI command 'show system setting fips-mode' if available.
    Affected if The device is running in non-FIPS configuration mode, which is required for this vulnerability to be exploitable.
  4. Assess authentication exposure
    Review which users have authenticated access to the WildFire appliance admin interface or CLI.
    Affected if Any authenticated users exist on the system, as the vulnerability requires authenticated user access to exploit the arbitrary file read/delete.

The environment is affected if it is a WildFire WF-500 or WF-500-B appliance running a PAN-OS version within the affected ranges AND operating in non-FIPS mode with authenticated user accounts present.

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.

From vendor data
Upgrade available Upgrade to 10.2.7 / 10.2.10 / 10.2.13 or later
Fixed in 10.2.710.2.1010.2.13
Interim mitigation

Apply the WildFire Appliance software update released by Palo Alto Networks to remediate this vulnerability in affected WF-500 and WF-500-B appliances.

Fix this in Pan Os Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,820
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0259 — 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-2026-0259 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