#paloaltonetworks

Read Time:3 Minute, 27 Second

Palo Alto Networks has disclosed an actively exploited PAN-OS vulnerability that can give a privileged attacker root-level code execution on affected firewalls. The flaw, tracked as CVE-2026-0322, targets the management interface and has received a CVSS 4.0 score of 8.6. The company describes observed exploitation as very limited, but has assigned its highest remediation urgency and advises customers to upgrade without delay.

The disclosure matters because a firewall is a central enforcement point for network traffic. Root access to the appliance can give an intruder exceptional visibility and control, potentially allowing configuration changes, persistence, or interference with security monitoring. Palo Alto Networks has not attributed the activity or said how many organizations were targeted.

How the PAN-OS flaw worksCVE-2026-0322 is a code-injection weakness classified as CWE-94. Exploitation requires network access to the PAN-OS management interface as well as an authenticated account with high privileges. A successful attacker can execute code as root without further user interaction.

Those prerequisites make this different from an unauthenticated internet-wide compromise. However, they do not make the issue harmless. Stolen administrator credentials, an insider, or an attacker who has already established a foothold could use the bug to turn limited access into full control of a security appliance. Internet-exposed management interfaces face the clearest risk.

Affected platforms include PA-Series hardware firewalls, VM-Series virtual firewalls, and Panorama on virtual systems or M-Series appliances. Palo Alto Networks says Cloud NGFW and Prisma Access are not affected. No unusual configuration is required for a vulnerable installation to be exposed to the weakness.

Fixed releases and affected branchesCustomers should consult the vendor advisory for the exact upgrade path for their branch. Fixed releases identified by Palo Alto Networks include:

PAN-OS 12.2.4;

PAN-OS 12.1.10-h2;

PAN-OS 11.1.16-h3;

PAN-OS 10.2.18-h12;

selected 11.2 hotfixes, including 11.2.4-h22, 11.2.7-h21, 11.2.10-h15, and 11.2.13-h3.

The vendor says there is no workaround that eliminates the flaw. Restricting the management interface to trusted internal addresses and reaching it through a hardened jump host can reduce exposure, but those controls are not substitutes for installing a corrected build.

Before upgrading, operators should back up the current configuration and follow the normal high-availability sequence so paired devices do not lose protection at the same time. Afterward, verify the reported software version, confirm that policy synchronization and traffic processing are healthy, and record the change in the asset inventory. Any appliance that cannot be patched immediately should have management access reduced to the narrowest possible set of source addresses and monitored continuously until remediation is complete.

What defenders should investigatePalo Alto Networks linked three IP addresses to threat activity and limited exploit attempts: 66[.]42[.]72[.]14, 208[.]83[.]239[.]114, and 149[.]248[.]47[.]234. Security teams should search firewall management and upstream network logs for connections involving those addresses, while remembering that attackers can change infrastructure and that an indicator match is not required for compromise.

Defenders should also review administrator logins, unexpected configuration changes, newly created accounts, unusual processes, and management traffic from hosts that do not normally administer the appliance. Where possible, compare local evidence with independent logging because an attacker operating as root may be able to alter records on the device.

Priorities for firewall ownersOrganizations should inventory every physical firewall, virtual instance, and Panorama deployment, including disaster-recovery and lab systems that may still be reachable. Confirm the running version rather than relying on asset records, then apply the vendor-recommended fixed release. Management access should be limited to a small group of dedicated administrative systems protected with strong authentication.

Finally, teams should treat patching and compromise assessment as parallel tasks. Installing an update closes the known route but does not prove that earlier exploitation did not occur. Because the vulnerable component protects the network itself, any suspicious evidence deserves a broader incident-response review of credentials, configurations, and traffic that passed through the device.

Read Time:3 Minute, 19 Second

Ransomware operators are exploiting an authentication bypass in Palo Alto Networks’ remote-access products to enter corporate environments through connections that can resemble ordinary employee VPN traffic. The flaw, tracked as CVE-2026-0257, affects certain configurations of PAN-OS GlobalProtect and Prisma Access and has reportedly been used by groups including Qilin and Settra.

The activity raises the stakes beyond a conventional perimeter vulnerability. Once an unauthorized session is established through an organization’s own VPN infrastructure, subsequent traffic inherits a degree of trust. Attackers can use that position to seek credentials, map the environment, move laterally, collect data, and prepare encryption while blending into a familiar remote-access channel.

Why the GlobalProtect flaw is dangerousCVE-2026-0257 is rated High with a CVSS score of 7.8. It can allow an unauthenticated attacker to bypass security controls and create a VPN connection, but exposure depends on how the service is configured. The vulnerable condition involves authentication override cookies together with a particular certificate setup. Consequently, administrators need to inspect their actual deployments rather than assume every appliance—or no appliance—is affected.

The affected product families include several maintenance releases across PAN-OS 12.1, 11.2, 11.1, and 10.2, as well as Prisma Access 11.2 and 10.2. Panorama and Cloud NGFW are not listed as affected. Because fixed status varies by maintenance release, teams should compare every portal and gateway with Palo Alto Networks’ version table.

Authentication override cookies are intended to simplify authentication between GlobalProtect components. The weakness arose because cookies could be trusted without sufficient validation and integrity protection under the relevant configuration. An attacker able to exploit that behavior could obtain access without presenting legitimate user credentials.

Ransomware activity follows initial VPN accessReliaQuest observed the flaw in activity associated with Qilin and Settra and reported related use of offensive tools including Cobalt Strike, BloodHound, and SharpHound. Those tools can support command and control, Active Directory discovery, and attack-path mapping. Their presence shows why a successful VPN connection should be treated as the beginning of an investigation, not the end of an authentication check.

Earlier reporting linked Qilin intrusions using the same flaw to credential theft and eventual ransomware deployment. Evidence of use by another operation suggests the technique is spreading beyond one crew, potentially through initial-access brokers or shared playbooks. ReliaQuest expects exploitation to remain attractive over the coming months as attackers search for exposed, unpatched gateways.

Patch every component and remove old accessOrganizations should apply the vendor’s fixed releases across all internal and external portals and gateways that issue or accept the affected cookies. Hybrid Prisma Access environments may also require updates to on-premises firewalls. A partial upgrade can cause cookie compatibility problems, so remediation should be planned as an environment-wide change.

Disable authentication override cookies wherever the feature is not required.

Create a dedicated new certificate for cookie signing and do not reuse portal, gateway, or other service certificates.

Terminate active GlobalProtect sessions after patching so pre-remediation access cannot simply continue.

Review unexpected devices, source addresses, login times, and unusual hostnames, then correlate them with endpoint and identity telemetry.

Users will need to authenticate again after the updated components begin generating new cookies. That inconvenience is important: installing a patch does not automatically evict an intruder who established a session earlier.

Detection must extend beyond the gatewaySecurity teams should hunt for activity after suspicious VPN logins, including credential dumping, directory enumeration, remote service use, new administrative accounts, unusual data staging, and connections to systems the user does not normally access. A device name such as “kali” can be a useful lead, but it is not proof by itself and should be evaluated with other evidence.

The broader lesson is that trusted access infrastructure becomes an effective disguise when attackers bypass its identity controls. Rapid patching closes the entry point; session invalidation and retrospective investigation determine whether the organization has actually removed the threat.