Skip to content
Reachability Analysis

Read an advisory phrase by phrase: the conditions sit in the description, the exposure note and the workaround

The summary block is the vendor's opinion, so decode each field

The advisory for CVE-2026-0322 opens with a summary block before any prose. The vendor supplies every field. The CVSS 4.0 specification defines the supplemental ones, and the vector at the foot of the page carries them as short codes.

Scroll the table sideways for more columns

Field and valueVector codeWhat it saysWhat it leaves open
Severity 8.6 HIGHAV:N/AC:L/AT:N/PR:H/UI:NNetwork attack, low complexity, no extra requirements, high privileges neededWhether anyone outside holds an administrator account
Exploit Maturity ATTACKEDE:AExploitation has been seenWhen it began and how many victims
Automatable NOAU:NAttackers cannot reliably automate all four kill chain steps across targetsWhether a determined attacker can still do it by hand
Recovery USERR:UA person must act to restore service after an attackWhether a root-level compromise can be undone by restoring service
Value Density DIFFUSEV:DThe vendor judges the system holds limited resources; the specification's example of concentrated is a central email serverYour view of a perimeter firewall, which is yours to make
Response Effort MODERATERE:MThe vendor expects a moderate effort to respondYour change window and outage cost
Urgency HIGHESTU:RedProvider Urgency, an optional supplemental metric in which the provider assesses "the highest urgency" (Red)Your own priority: the value is the provider's pass-through assessment, and your exposure, accounts and change window still set your action

The description holds two conditions, a scope sentence and one mitigation

The description says an "authenticated attacker with network access" can run arbitrary code "with root privileges". That is two conditions, a network path to the management interface and a valid account, plus the impact. Read "root" as full device control, not as a service-level compromise.

The scope sentence is the one that decides step 1: the issue applies to PAN-OS on PA-Series and VM-Series firewalls and on Panorama, virtual and M-Series. "Cloud NGFW and Prisma Access are not impacted." A finding raised on a hosted service closes here.

The sentence that follows, saying risk is minimized by restricting management access to trusted internal IP addresses, is a mitigation placed in the description. It is easy to skip, and it is the only workaround-like text outside the workarounds section.

"Required Configuration for Exposure" says none, then adds a second reading

The section opens with "No special configuration is required to be affected by this issue." Default builds are in scope, so a clean configuration review cannot close the finding. The next sentence says the risk is highest when management access is allowed from external IP addresses on the internet.

The advisory prices the difference. Restricting access to a single jump box changes the vector from AV:N to AV:A and lowers the CVSS-B and CVSS-BT, both 8.6, to 8.5. The vendor therefore treats a jump box as a small reduction, not as removal of the exposure.

The product status table and the solution table cut versions differently

Product Status lists affected ranges per sub-train, such as "< 11.2.10-h15". The Solution table lists the running range and the build to move to. A firewall on 11.2.10-h9 sits in "11.2.8 through 11.2.10-h*", where the "h*" covers any hotfix, and the answer is "Upgrade to 11.2.10-h15 or 11.2.16 or later." Moving it to 11.2.7-h21, which is the target for a lower range, would be a downgrade.

The last row, "All older unsupported PAN-OS versions", says "Upgrade to a supported fixed version." It means a firewall on an end-of-life release is affected and has no patch on its own train.

"Very limited exploitation has been observed" gives no date

The Exploitation Status section is one sentence. Together with Exploit Maturity ATTACKED it supports step 4 of a triage record, but it names no start date. CISA's KEV entry, dated 14 Oct 2026 and the same day as publication, is the dated fact to cite. The page also says the issue was discovered internally and shows an update on 15 Oct 2026, the date to store as the revision you read.

"Very limited" describes what the vendor has seen. It is not a statement about what is possible against your build.

"No known workarounds exist" is followed by a conditional signature

The workarounds section says no workaround exists, then offers Threat IDs 510046 and 510047 from content version 9159-10287. They work only if management traffic is routed through a data-plane port, the certificate is replaced, inbound traffic is decrypted and threat prevention is enabled. The FAQ explains "limited coverage": variations may exist that the signature cannot detect, and the vendor recommends upgrading. Record such signatures as detection, not as a closing reason.

The FAQ also lists three IP addresses tied to exploit attempts. They are useful for log searches, and an empty result does not show the device is clean.

The same phrases in other vendors' advisories

Stock phrases recur across vendors. Read the phrase, then read what surrounds it.

Phrase and sourceWhat it saysWhat to do
"regardless of device configuration" (Cisco, CVE-2026-76460)No configuration removes exposurePatch, and restrict access to the nodes; the advisory's mitigation is infrastructure access control lists
"There are no workarounds that address this vulnerability. However, there is a mitigation." (Cisco)A control reduces remote exploitation but is temporaryRecord it as mitigation with a date, and keep the upgrade ticket open
"The Cisco PSIRT is aware of active exploitation" (Cisco)Exploitation exists, no date givenCite the advisory revision, then check KEV for a date
"under certain conditions" (GitLab, CVE-2026-97229)A condition exists and is not stated; the phrase appears on several other entries in the same release too, so it carries no signalTreat reachable self-managed instances as exposed and patch to 19.4.2, 19.3.5 or 19.2.8
"Under the right conditions" (BeyondTrust BT26-05, CVE-2026-102764)A condition exists and details are withheldApply the patch; check for earlier compromise
"Affected Atlassian Cloud products have been patched" and "No Cloud customer action is required" (Atlassian, CVE-2026-21589)The vendor patched the hosted serviceScope work to Data Center, Crucible and Fisheye
"Exploitation requires prior knowledge of the target file's exact name and path" (Atlassian)A real precondition that limits impactRecord it, and still patch: the advisory says some configurations hold sensitive files
"reported to be exploited in the wild, customers are urged to apply the workaround below" (Fortinet FG-IR-26-175, CVE-2026-104286)Exploited, and the workaround is the first actionDisable the IBE service or limit webmail access today, then upgrade
"Upgrade to upcoming 7.2.10 or above" and "Migrate to a fixed release" (Fortinet)No fixed 7.2 build yet; 7.0 gets noneApply the workaround and track the date
"need not perform any action" for FortiMail Cloud, remediated 5 Oct 2026 (Fortinet)Hosted service fixed after the 1 Oct 2026 publication; the timeline shows a clarification on 7 Oct 2026Store the remediation date from the advisory

Fixed-version text needs your release line, not the headline number

Fortinet lists a separate fix for each FortiMail line: 8.0.2, 7.6.7 and 7.4.9. BeyondTrust ties the patch to a version range: the BT26-05 patch covers 24.3.1 to 26.2.3, and installs older than 24.3.1 must upgrade first. Copy the line that matches the running build, and record the exact build after patching, since "patched" without a version cannot be checked later.

A record line for the CVE-2026-0322 advisory, as stored on 19 Nov 2026: CVE-2026-0322, PAN-OS, advisory updated 15 Oct 2026; CVSS-B 8.6, vector CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:A/AU:N/R:U/V:D/RE:M/U:Red; conditions: network path to the management interface and a high-privilege account; scope: PA-Series, VM-Series, Panorama, not Cloud NGFW or Prisma Access; exploitation: ATTACKED, no start date, KEV 14 Oct 2026; fix: the build for the running sub-train, for example 11.2.10-h15 or 11.2.16 on 11.2.8 to 11.2.10-h*; workaround: none, Threat IDs 510046 and 510047 as detection only.

Sources

  1. Palo Alto Networks advisory for CVE-2026-0322, read 19 Nov 2026
  2. FIRST CVSS v4.0 specification document, read 19 Nov 2026
  3. CISA KEV JSON feed, release 2026.11.18, read 19 Nov 2026
  4. Cisco advisory for CVE-2026-76460, read 19 Nov 2026
  5. GitLab patch release 19.4.2, read 19 Nov 2026
  6. BeyondTrust advisory BT26-05, read 19 Nov 2026
  7. Atlassian advisory for CVE-2026-21589, read 19 Nov 2026
  8. Fortinet advisory FG-IR-26-175, read 19 Nov 2026

Last reviewed 19 Nov 2026.