Palo Alto Networks publishes Idira Java fixes; PAN-OS excluded

← Security Watch

The useful question for this Java advisory is which privileged-access product needs an upgrade. Palo Alto Networks now lists Idira fixes while explicitly excluding PAN-OS products for CVE-2026-114938.

Conceptual illustration of protected remote access, server modules and a magnifying inspection ring.

What is new

New Palo Alto Networks portfolio advisory for CVE-2026-114938, verified November 19, 2026, Eastern. Its JSON datePublic and CSAF initial release are November 20, 2026 at 00:30 UTC (November 19 at 7:30 p.m. Eastern). The HTML shows Published November 20, Updated November 19, and a November 19 initial-publication timeline; the CSAF revision-history time differs again. These inconsistent date fields do not establish a separate later fix.

Vendor facts: Critical, CVSS 4.0 base 9.2; vendor suggested urgency Moderate. My suggested MSP priority is High when an affected Idira deployment and relevant processing path are confirmed. Do not assume any customer operates these products.

Check the exact product and build

Idira productAffected branch / rangeVendor upgrade target
Remote Access ConnectorBefore 1.1.1002202; CPE range starts at 1.1.01.1.1002202 or later
Remote Access Connector CLIBefore 1.1.3701; CPE range starts at 1.1.01.1.3701 or later
Secure Access with an HTML5 Gateway (On-Prem), 15.2.215.2.2.0–15.2.2.1615.2.2.17 or later
Secure Access with an HTML5 Gateway (On-Prem), 15.0.315.0.3.0–15.0.3.2015.0.3.21 or 15.2.2.17 or later
Privilege Threat Analytics, 15.215.2.0–15.2.215.2.3 or later
Privilege Threat Analytics, 15.0All 15.0 releases listed affected; no fixed 15.0 build listedMove to 15.2.3 or later
Privilege Threat Analytics, 14.614.6.0–14.6.314.6.4 or 15.2.3 or later

These are vendor-documented upgrade targets, not proof a customer has installed or loaded a fix. The solution table and CPE ranges provide branch detail; the autogenerated CSAF uses broad version expressions, so do not interpret every later version as vulnerable or every unlisted older branch as cleared. Confirm supported package access and the upgrade path with the vendor.

Exposure and exploitation

The flaw is an out-of-bounds heap write in the optimized Base64 decoder of an affected HotSpot JVM. Exploitation requires an affected Java runtime, x86-64 hardware with AVX-512 VBMI and enabled Base64 intrinsics, plus an application path that decodes attacker-controlled Base64 input. This can lead to unauthenticated remote code execution in an affected application.

The advisory also says no special configuration is required. Read that alongside the explicit runtime, hardware and input-path prerequisites; it does not establish exposure for every Java application or every installation.

Palo Alto Networks says it is not aware of malicious exploitation. CVE-2026-114938 is absent from the full CISA KEV catalog checked for this review; there is no KEV addition date or federal deadline to report. A proof of concept or an exploitability score would not, by itself, establish an attack against Idira.

PAN-OS and cloud status

The vendor says there is no impact on PAN-OS-based NGFW hardware PA-Series, VM-Series and AIRS, Panorama M-Series and VM, WF-500-B, or the PAN-DB private-cloud appliance. This exclusion applies to this CVE, not to all security advisories.

The vendor lists the following as addressed cloud/SaaS products with no customer action required: ADEM Infrastructure, Prisma Access – MSP, Prisma AIRS, Idira – EPM SaaS, Idira – Remote Access, and Idira – Secure Access with an HTML5 Gateway. Customer-managed connectors and on-premises components still need their own applicability check. The portfolio investigation continues.

MSP action sequence

Inventory: identify actual Idira product, branch, installed build, runtime/CPU and untrusted Base64 processing path across customer environments. Separate SaaS service status from customer-managed components and third-party integrations.

Contain where warranted: reduce unnecessary access to an affected processing or management path while arranging the supported upgrade. This is a suggested exposure-reduction step, not a vendor workaround. Palo Alto Networks lists no known workaround.

Upgrade: use the relevant product fix above; migrate Privilege Threat Analytics 15.0 to 15.2.3 or later. Follow supported vendor procedures rather than replacing bundled Java independently.

Verify: confirm the running component reports the fixed build after the required service restart or redeployment, then test remote-access, privileged-access and analytics workflows. Track failed or deferred upgrades per customer. If suspicious activity exists, preserve evidence and investigate separately; this advisory supplies no new blanket credential-rotation or compromise-check requirement.

Official sources and limits

Palo Alto Networks advisory, solution matrix and FAQ · Vendor JSON · Vendor CSAF/VEX · CISA official full KEV data.

Last verified November 19, 2026, Eastern. This is an applicability and remediation review, not confirmation of customer exposure, successful patch deployment or an all-clear across sources with access gaps.

Share this article