dbcve.org
Prisma Sd WanApplication · Paloaltonetworks

CVE-2026-0244

HIGH · 8.1 CVSS v3.1 Published 2026-05-13
Fix available
A fix is available. Upgrade to 6.3.6 / 6.4.3 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 improper certificate validation vulnerability in the Palo Alto Networks Prisma SD-WAN ION enables man-in-the-middle (MitM) attacker to impersonate the controller.

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 confidence

Improper certificate validation vulnerability in Palo Alto Networks Prisma SD-WAN ION devices allows man-in-the-middle attackers to impersonate the controller by failing to properly validate certificates during the authentication process.

MitigationUpdate to the latest Prisma SD-WAN ION version as patches become available; verify that proper certificate chain validation and hostname verification are enforced.

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
Prisma Sd WanApplication
Affected:>= 6.3.1, < 6.3.6>= 6.4.1, < 6.4.3>= 6.5.1, < 6.5.3= 6.3.6= 6.4.3= 6.5.3

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 ION device version
    Access the Prisma SD-WAN administrative interface or use the CLI command to display the installed ION software version. Common methods include the web UI dashboard or running 'show version' via CLI.
    Affected if The installed version falls within 6.3.1 to 6.3.6, 6.4.1 to 6.4.3, or 6.5.1 to 6.5.3 (including the specific versions 6.3.6, 6.4.3, and 6.5.3)
  2. Verify controller connectivity is enabled
    Check the ION device configuration to determine if it is configured to communicate with a Prisma SD-WAN controller. This is typically found in the network or controller settings of the ION web UI or via CLI.
    Affected if The ION device has an active controller connection configured and enabled, as the vulnerability only applies when ION-to-controller communication is in use
  3. Inspect SSL/TLS certificate validation settings
    Review the SSL/TLS and certificate validation settings for the controller connection. This is usually configurable in the ION security or controller settings. Look for options controlling certificate chain validation, hostname verification, or trust store configuration.
    Affected if Certificate validation is disabled, set to optional, or otherwise not enforced for the controller connection
  4. Check for active controller sessions
    View the current active sessions or connections between the ION and its designated controller. Use the administrative interface to list established controller connections.
    Affected if An active unencrypted or improperly validated SSL/TLS session exists between the ION and controller, indicating the vulnerability is exploitable in the current traffic flow

The environment is affected if the installed Prisma SD-WAN ION version is one of the vulnerable versions listed AND the ION is configured to communicate with a controller using SSL/TLS with certificate validation disabled or not properly enforced.

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 6.3.6 / 6.4.3 / 6.5.3 or later
Fixed in 6.3.66.4.36.5.3
Interim mitigation

Update to the latest Prisma SD-WAN ION version as patches become available; verify that proper certificate chain validation and hostname verification are enforced.

Recommended fix Moderate confidence

Upgrade to the latest stable release in your current version branch (6.3.7+, 6.4.3+, or 6.5.3+)

  1. 1. Identify the current Prisma SD-WAN ION software version by navigating to the SD-WAN dashboard or checking the device management interface.
  2. 2. Determine which version branch (6.3.x, 6.4.x, or 6.5.x) your devices are currently running.
  3. 3. For branch 6.3.x: Upgrade to version 6.3.7 or later.
  4. 4. For branch 6.4.x: Upgrade to version 6.4.3 or later.
  5. 5. For branch 6.5.x: Upgrade to version 6.5.3 or later.
  6. 6. Download the appropriate upgrade image from the Palo Alto Networks support portal.
  7. 7. Apply the upgrade during a planned maintenance window, following standard SD-WAN upgrade procedures.
  8. 8. After upgrade, verify the controller connection is re-established successfully and monitor for any connectivity issues.

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

Fix this in Prisma Sd Wan Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing16.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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