CVE-2026-0282
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 · uneditedA file deletion vulnerability in Palo Alto Networks PAN-OS® software enables an unauthenticated attacker with network access to the management web interface to delete files from a temporary directory. The security risk posed by this issue is minimized by restricting access to the management web interface to only trusted internal IP addresses according to our recommended best practice 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 is applicable to PAN-OS software on PA-Series and VM-Series firewalls and on Panorama (virtual and M-Series). Cloud NGFW and Prisma® Access 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 · moderate confidenceA file deletion vulnerability in Palo Alto Networks PAN-OS software allows an unauthenticated attacker with network access to the management web interface to delete files from a temporary directory. This affects PA-Series and VM-Series firewalls and Panorama (virtual and M-Series 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>= 10.2.0, < 11.1.16>= 11.2.0, < 11.2.13>= 12.1.0, < 12.1.8CVSS 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
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the PAN-OS version installedAccess the firewall or Panorama CLI and run 'show system info' or check via the web interface under Device > Setup > Operations. Alternatively, use the API endpoint '/api/?type=op&cmd=<show><system><info/></system></show>&key=YOUR_API_KEY'Affected if The displayed version falls within these ranges: 10.2.0 to 11.1.15 (inclusive), 11.2.0 to 11.2.12 (inclusive), or 12.1.0 to 12.1.7 (inclusive)
-
Confirm the management web interface is enabledCheck the management interface configuration via CLI using 'show interface management' or inspect the network profile settings under Device > Setup > Management in the web UIAffected if The management web interface (HTTPS on port 443 by default) is enabled and configured on any physical or virtual management port
-
Verify network accessibility of the management interfaceDetermine if the management interface is reachable from untrusted networks. Review the 'Management' profile in Network > Network Profiles > Interface Management or check routing and firewall policy allowing external access to port 443/TCP on the management IPAffected if The management web interface is accessible from network segments outside trusted internal IP addresses, or is directly exposed to the internet
A user is affected if their PAN-OS version matches any of the affected ranges AND the management web interface is network-accessible to untrusted sources, since the vulnerability can be exploited without authentication.
Generated from the published advisory. Verify against your own configuration.
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 · scoped11.1.1611.2.1312.1.8
Restrict access to the management web interface to only trusted internal IP addresses according to Palo Alto Networks best practice deployment guidelines.
11.1.16 or later (if on 10.2.x); 11.2.13 or later (if on 11.2.x); 12.1.8 or later (if on 12.1.x)
- 1. Identify your current PAN-OS version by navigating to Device > Summary in the web interface
- 2. Download the appropriate PAN-OS update from the Palo Alto Networks Customer Support Portal (https://support.paloaltonetworks.com)
- 3. For Panorama deployments: Upload the update to Panorama > Device Deployment > Software
- 4. For firewall deployments: Upload the update to Device > Software > Upload
- 5. Install the update: Device > Software > Install and select the target device(s)
- 6. After installation, verify the version by checking Device > Summary to confirm the system is running a fixed version (11.1.16+, 11.2.13+, or 12.1.8+)
- 7. As a secondary mitigation per Palo Alto best practices, restrict management web interface access to trusted internal IP addresses only
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0282 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-0282 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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