dbcve.org
Pan OsOperating system · Paloaltonetworks

CVE-2026-0265

HIGH · 8.1 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 →
90/100
Remediation priority · Urgent
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 vulnerability in Palo Alto Networks PAN-OS® software enables an unauthenticated attacker with network access to bypass authentication controls when Cloud Authentication Service (CAS) is enabled. The risk is higher if CAS is enabled on the management interface and lower when any other login interfaces are used. The risk of this issue is greatly reduced if you secure access to the management web interface by restricting access 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 · high confidence

An authentication bypass vulnerability in PAN-OS allows an unauthenticated attacker with network access to bypass authentication controls when Cloud Authentication Service (CAS) is enabled. The vulnerability has higher impact when CAS is enabled on the management interface.

MitigationRestrict access to the management web interface to trusted internal IP addresses only, or disable CAS on the management interface if not required.

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
Ruggedcom Ape1808 FirmwareOperating system
Affected:all versions

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

CVSS:3.1/AV:N/AC:H/PR:N/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. Identify the PAN-OS version
    Locate the installed PAN-OS version in the firewall or Panorama web interface under Device > Setup > Operations or via the CLI command 'show system info'
    Affected if The version falls within any of these ranges: < 10.2.7, 10.2.8-10.2.9, 10.2.11-10.2.12, 10.2.14-10.2.15, 10.2.16-10.2.18, 11.1.0-11.1.3, or 11.1.5-11.1.5 (meaning any version listed as affected in the CVE advisory)
  2. Confirm product type is affected
    Verify the device is a PA-Series firewall, VM-Series firewall, Panorama virtual appliance, or M-Series appliance. Check the model number in the hardware label or system info
    Affected if The device is any of these types (Cloud NGFW and Prisma Access are not affected)
  3. Verify if Cloud Authentication Service (CAS) is enabled
    Check the PAN-OS web interface under Device > Cloud Authentication Service or examine the authentication profile configuration to determine if CAS is configured and active
    Affected if CAS is enabled and configured on the device (this is a required condition for the vulnerability to be exploitable)
  4. Determine if CAS is applied to the management interface
    Review the interface configuration to see whether CAS authentication is assigned to the management web interface (MGMT) versus other login interfaces
    Affected if CAS is specifically applied to the management interface (this configuration elevates the exploit risk per the CVE description)

The environment is affected if the device runs an affected PAN-OS version, is a PA-Series/VM-Series/Panorama/M-Series model, and has Cloud Authentication Service enabled (especially on the management interface).

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.2.7 / 10.2.10 / 10.2.13 or later
Fixed in 10.2.710.2.1010.2.13
Interim mitigation

Restrict access to the management web interface to trusted internal IP addresses only, or disable CAS on the management interface if not required.

Recommended fix Moderate confidence

PAN-OS 10.2.16 or later (for PA-Series, VM-Series, and Panorama)

  1. 1. Identify all Palo Alto Networks PAN-OS devices in your environment running affected versions (< 10.2.7, 10.2.8-10.2.9, 10.2.11-10.2.12, 10.2.14-10.2.15)
  2. 2. Identify if Cloud Authentication Service (CAS) is enabled on any affected devices via the PAN-OS web interface under Device > Cloud Authentication Service
  3. 3. For each affected PAN-OS device, plan an upgrade to version 10.2.16 or later (the first fixed release)
  4. 4. Before upgrading, backup the PAN-OS configuration via Device > Setup > Operations > Save named configuration snapshot
  5. 5. Execute the PAN-OS upgrade following standard upgrade procedures: download the update from Palo Alto Networks support portal, upload to device, and install
  6. 6. After upgrade, verify CAS functionality continues to work as expected
  7. 7. For Ruggedcom Ape1808 devices, check cert-portal.siemens.com for firmware updates or contact Siemens support for remediation guidance
  8. 8. As an additional mitigation before patching, restrict access to the management web interface to trusted internal IP addresses only (Device > Management > Interface Settings)
Caveat Review PAN-OS upgrade guide for any migration considerations between your current and target version; test in non-production first

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

Fix this in Pan Os Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
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,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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