3. Description
Palo Alto Networks has assessed the impact of CVE-2026-109618 and the related CVE-2026-109619 on its products. Both vulnerabilities involve PHP memory-handling failures that can potentially lead to remote code execution.
CVE-2026-109618 occurs when PHP handles out-of-memory conditions through longjmp() without correctly managing request memory initialization. This can leave memory in an unsafe state and create an opportunity for an attacker to trigger remote code execution.
CVE-2026-109619 concerns a different failure in fatal-error handling. Global memory references may continue to point to memory that has already been freed, allowing subsequent requests to read or branch on invalid memory.
For Palo Alto Networks customers, the principal concern is exposure of the PAN-OS management interface. An internet-accessible management interface presents a higher risk than one restricted to trusted internal systems. The vendor recommends limiting access to approved internal IP addresses and implementing its published mitigation measures while affected PAN-OS versions await fixes.
The advisory also identifies numerous Palo Alto Networks products as unaffected and notes that remediation patches had already been deployed for certain cloud services that were previously impacted.
4. Technical Description
Vulnerability: CVE-2026-109618
Related vulnerability: CVE-2026-109619
Affected technology: PHP memory and error handling
Affected Palo Alto Networks products: Specific PAN-OS versions running on PA-Series and VM-Series firewalls and Panorama virtual and M-Series appliances
Vulnerability type: Remote code execution
Weakness classification: CWE-754 — Improper Check for Unusual or Exceptional Conditions
Attack vector: Network
Attack complexity: Low, according to the Palo Alto Networks product assessment
Privileges required: None, according to the product assessment
User interaction: None, according to the product assessment
Palo Alto Networks severity: HIGH
Palo Alto Networks CVSS-B score: 8.7
Vendor CVSS-B score: 9.2
Reported exploitation status: Palo Alto Networks stated that it was not aware of malicious exploitation against its products at the time of the advisory update.
Primary security concern: Potential loss of availability through remote code execution affecting the management interface.
5. Vulnerability Overview
5.1 CVE-2026-109618: Improper memory handling during out-of-memory errors
The vulnerability arises from how PHP handles exceptional memory conditions.
When an out-of-memory error occurs, PHP may use longjmp() to transfer control away from the failing execution path. According to the advisory, improper control-flow management can leave request memory uninitialized.
An attacker may trigger out-of-memory conditions to exploit this unsafe state and potentially achieve remote code execution.
The core issue is not simply that memory is exhausted. It is that the error-handling path may leave memory in an unsafe condition that can be exploited.
5.2 CVE-2026-109619: References to freed memory
The related vulnerability involves fatal-error handling that leaves global memory references pointing to freed memory regions.
Subsequent requests may interact with those invalid references. Depending on the resulting memory state, this can enable arbitrary code execution.
Although both vulnerabilities involve PHP error handling and memory safety, they represent distinct failure conditions and should be tracked separately.
5.3 Why management-interface exposure matters
Palo Alto Networks identifies the PAN-OS management interface as the primary concern for its affected products.
The interface includes:
The HTTPS-based management web interface.
The XML API service.
The vendor states that the risk is highest when management access is permitted from external internet addresses. Restricting access to trusted internal IP addresses—and preferably through a dedicated jump box—reduces exposure.
The advisory does not state that every PAN-OS deployment is equally exposed. Actual risk depends on the affected software version, interface exposure, and applied mitigations.
6. Technical Analysis
6.1 How the memory-handling flaw works
The reported failure involves the interaction between error handling and memory state.
Under normal conditions, an application must correctly manage memory when an operation fails. If an out-of-memory condition causes execution to jump to an error-handling path, the application must ensure that request-specific data is properly initialized before it is used again.
For CVE-2026-109618, Palo Alto Networks describes a control-flow problem that can leave request memory uninitialized after longjmp() handles an out-of-memory error.
This unsafe state may create conditions for an attacker to influence subsequent execution and achieve remote code execution.
For CVE-2026-109619, the problem is instead that global memory references can continue to point to freed memory. Later requests may access or branch on these stale references.
Both cases demonstrate how exceptional error paths can become security boundaries: if memory state is not safely restored, an error-handling mechanism can introduce an exploitable condition.
6.2 Affected Palo Alto Networks products
The advisory identifies specific affected PAN-OS release branches. The listed thresholds below reflect the vendor's October 24, 2026 advisory and should be checked again before deployment decisions.
| PAN-OS branch | Affected versions listed by vendor | Fixed-version threshold listed by vendor |
|---|---|---|
| PAN-OS 12.2 | Below 12.2.4-h1 | 12.2.4-h1 or later |
| PAN-OS 12.1 | Below 12.1.4-h13, 12.1.7-h11, or 12.1.10-h3, according to the applicable maintenance branch | Corresponding listed hotfix threshold or later |
| PAN-OS 11.2 | Below 11.2.4-h23, 11.2.7-h23, 11.2.10-h16, 11.2.13-h4, or 11.2.16-h1, according to the applicable maintenance branch | Corresponding listed hotfix threshold or later |
| PAN-OS 11.1 | Below 11.1.4-h38, 11.1.6-h40, 11.1.7-h12, 11.1.10-h36, 11.1.13-h16, or 11.1.16-h4, according to the applicable maintenance branch | Corresponding listed hotfix threshold or later |
| PAN-OS 10.2 | Below 10.2.7-h39, 10.2.10-h42, 10.2.13-h27, 10.2.16-h12, or 10.2.18-h13, according to the applicable maintenance branch | Corresponding listed hotfix threshold or later |
Important: These thresholds must be interpreted within the relevant PAN-OS maintenance branch. Do not select a version solely from this summary; consult the official advisory for the precise release applicable to the installed version and device.
The advisory lists the following product groups as unaffected:
Bridgecrew
Cloud NGFW
Cortex XDR Agent
Cortex XDR Broker VM
Cortex XSIAM
Cortex XSOAR
Cortex Xpanse
GlobalProtect App
Prisma Access
Prisma Access Agent
Prisma Cloud
Prisma SD-WAN Controller
Prisma SD-WAN ION
Prisma SD-WAN On-Prem Controller
Strata Cloud Manager
WildFire Appliance WF-500 and WF-500-B
The advisory also records remediation patches deployed for Cortex XCORE (SaaS) on October 21, 2026, and WildFire Cloud on October 22, 2026. Product status can change as the vendor updates its assessment.
6.3 Interfaces and configurations in scope
Palo Alto Networks states that no special configuration is required for a product to be affected by the underlying issue.
For PAN-OS and Panorama, the concern is specifically the management interface. The vendor confirms that:
The HTTPS management web UI is affected.
The XML API service is affected.
GlobalProtect portal, gateway, and Clientless VPN are not affected.
Captive Portal is not affected.
A dataplane interface is affected only if a management profile is attached to it.
This distinction matters when determining exposure. A deployment should be assessed according to its actual management-interface configuration rather than assuming every network interface is vulnerable.
6.4 Severity and exploitability
Palo Alto Networks lists the following risk information for its products:
| Metric | Vendor assessment |
|---|---|
| Severity | HIGH |
| CVSS-B | 8.7 |
| Attack vector | Network |
| Attack complexity | Low |
| Attack requirements | None |
| Privileges required | None |
| User interaction | None |
| Primary impact | High availability impact |
| Suggested urgency | Moderate |
The vendor's separate CVSS-B score for the underlying PHP vulnerability is 9.2.
The different scores reflect different assessment contexts. The underlying PHP vulnerability and its impact on a specific vendor product should not automatically be assigned identical risk scores.
6.5 Exploitation status
As of the advisory update dated October 24, 2026, Palo Alto Networks stated that it was not aware of malicious exploitation of this issue against its products.
This statement describes the vendor's reported visibility at that time. It does not establish that exploitation is impossible or that every potentially affected environment is safe.
Organizations should continue to apply the recommended exposure reductions and monitor the vendor's advisory for updated information.
7. Indicators of Compromise (IOCs)
No campaign-specific IP addresses, domains, URLs, or file hashes are provided in the Palo Alto Networks advisory as indicators of compromise for this vulnerability.
CVE-2026-109618 is a vulnerability identifier, not an IOC.
For detection and investigation, defenders should prioritize:
Unusual or unexpected connections to management interfaces.
Suspicious requests to the PAN-OS HTTPS management interface or XML API.
Unexpected management-plane service behavior.
Unexplained firewall management interruptions or availability degradation.
Relevant system, authentication, management, and network logs surrounding suspicious activity.
These are investigation priorities, not confirmed indicators published by the vendor. Do not create block rules or label arbitrary addresses as malicious without supporting evidence.
8. Potential Impact
8.1 Remote code execution
Successful exploitation may allow an attacker to execute code in the affected software context. The exact consequences depend on the affected component and its privileges.
8.2 Management-plane availability disruption
Palo Alto Networks assigns a high availability impact to the product-specific vulnerability assessment. Exploitation could disrupt access to the affected management interface and interfere with administrative operations.
8.3 Exposure of internet-accessible management services
Deployments that permit management access from public internet addresses face greater risk than deployments restricted to trusted internal addresses.
8.4 Operational disruption
If a management interface becomes unavailable, administrators may experience difficulties managing the affected firewall or Panorama environment. Incident response and recovery may require additional time and operational resources.
8.5 Security-management risk
A compromised management component could undermine confidence in administrative operations. The actual consequences would depend on the affected service, permissions, and what the attacker successfully executes.
These are potential impacts based on the vendor's vulnerability description and severity assessment, not confirmation that exploitation has occurred.
9. Recommendations
9.1 Immediate Actions
Identify affected versions: Inventory PAN-OS releases running on PA-Series and VM-Series firewalls and on Panorama virtual and M-Series appliances.
Review management-interface exposure: Determine whether the HTTPS management interface or XML API is accessible from external internet addresses.
Restrict management access: Limit access to trusted internal IP addresses and use a dedicated jump box as the only permitted management entry point where practical.
Apply available fixes: Follow the official Palo Alto Networks advisory to identify and install the appropriate fixed release for each device and maintenance branch.
Enable the vendor's recommended protections: Customers with an eligible Threat Prevention subscription should review the relevant Threat IDs and ensure that the required traffic routing, certificate replacement, decryption, and threat-prevention settings are configured.
Review management-plane logs: Investigate unexpected requests, unexplained management-service interruptions, and other suspicious activity. Preserve relevant evidence for incident response.
Verify product scope: Confirm whether the affected component is PAN-OS or Panorama management functionality rather than assuming that GlobalProtect or Captive Portal is affected.
Monitor vendor updates: Recheck the advisory for revised fixed versions, product status, and mitigation instructions before closing the vulnerability assessment.
9.2 Preventive Actions
Adopt least-privilege management access: Restrict administrative interfaces to approved users, devices, and network segments.
Avoid direct public exposure: Do not expose firewall management interfaces directly to the internet when a restricted internal or jump-box-based management architecture is available.
Maintain a patch-management process: Track firewall and Panorama versions, vendor advisories, maintenance windows, and deployment verification.
Harden management networks: Separate management traffic from ordinary user and public-facing traffic.
Monitor administrative activity: Retain and review authentication logs, management API access, configuration changes, and unexpected service behavior.
Validate security-control coverage: Confirm that relevant Threat Prevention protections are enabled and that the required traffic is routed through the inspection path.
Test recovery procedures: Maintain documented recovery and access procedures in case a management service becomes unavailable.
Reassess after updates: Verify installed versions and management-interface accessibility after remediation, and document any residual exposure.
10. Mitigation Details
Palo Alto Networks provides specific mitigations for customers awaiting fixed PAN-OS releases.
10.1 Restrict access to trusted systems
The vendor recommends limiting access to the management interface to trusted internal IP addresses. Restricting management access to a dedicated jump box further reduces the number of systems that can reach the interface.
10.2 Apply Threat Prevention coverage
The advisory lists Threat ID 543004 and additional Threat Prevention IDs for eligible customers using Applications and Threats content version 9162, 9163, 9164, and later.
The advisory specifies the following requirements for this protection:
Route incoming traffic for the management port through a dataplane port, for example by enabling a management profile on a dataplane interface.
Replace the certificate used for inbound traffic management.
Decrypt inbound traffic to the management interface so the firewall can inspect it.
Enable Threat Prevention on inbound traffic to management services.
The vendor also notes that eligible PAN-OS 12.2.4-and-later customers with Frontier Virtual Patching (ATP Plus) received advance coverage through Threat ID 543004.
Customers should follow the official vendor instructions and confirm that their configuration meets all prerequisites. Enabling a Threat ID alone may not provide the intended coverage if traffic bypasses the required inspection path.
11. Conclusion
CVE-2026-109618 highlights how memory-management failures in error-handling paths can create serious security risks. The related CVE-2026-109619 demonstrates a separate but similarly concerning condition involving references to freed memory.
For Palo Alto Networks customers, the immediate priority is to determine whether affected PAN-OS or Panorama versions are deployed and whether management interfaces are exposed to untrusted networks. Restricting management access, applying vendor-recommended mitigations, and installing the appropriate fixed release are central to reducing risk.
Although Palo Alto Networks reported no known malicious exploitation against its products as of October 24, 2026, organizations should not interpret that status as a reason to delay remediation. Management interfaces are sensitive administrative entry points and should remain accessible only to authorized systems.
A disciplined response—accurate version identification, reduced network exposure, effective inspection, and verified patch deployment—will help organizations manage the risk while the vendor continues updating its advisory.
