Published 20 November 2026 · Rathish Kumar, Invitty

Palo Alto Networks first published its status page for Java4Shell (CVE-2026-114938) on 19 November 2026. The short version: PAN-OS firewalls, Panorama, WF-500-B and the PAN-DB private cloud appliance are not affected. Self-hosted Idira components, the former CyberArk products, are. If you run Privilege Threat Analytics, the on-prem HTML5 Gateway or the Remote Access Connector, upgrade them to the fixed builds listed below.

Is PAN-OS affected by Java4Shell?

No. Palo Alto answers this directly in the advisory's FAQ: there is no impact on PAN-OS based products, which it lists as hardware PA-Series, VM-Series and AIRS firewalls, Panorama on M-Series and VM, the WF-500-B and the PAN-DB private cloud appliance. So the PA-440 in your branch and the PA-1410 at head office do not need an emergency change window for this one. (If you are planning a Palo Alto refresh anyway, nothing here changes that plan.)

That matters because the first question most firewall owners ask after a big Java flaw is whether the firewall is the next Log4Shell. For Palo Alto, it is not. Where you still have work is the identity side, and any Java tool you have bolted on to the firewall yourself, such as a log forwarder or a reporting server. Palo Alto says third-party and custom Java integrations remain the customer's job to patch.

Which Idira (CyberArk) components need an upgrade?

Idira is the name Palo Alto now uses for the CyberArk identity security platform it acquired. Its Idira page tells existing CyberArk customers they can keep using the platform as before, with a new logo and design. So the CyberArk modules you bought now appear in advisories under the Idira name.

Four self-hosted components are on the affected list. Privilege Threat Analytics (PTA) watches privileged sessions for risky behaviour. The HTML5 Gateway lets admins open RDP and SSH sessions from a browser. The Remote Access Connector, with its CLI, is the piece you install on site for Idira's Remote Access service.

CVE-2026-114938: affected Idira components and fixed buildsScroll sideways to see the full table
ComponentAffectedUpgrade to
Privilege Threat Analytics 15.215.2.0 to 15.2.215.2.3 or later
Privilege Threat Analytics 15.0All 15.0 builds, no fix on this branch15.2.3 or later
Privilege Threat Analytics 14.614.6.0 to 14.6.314.6.4, or 15.2.3 or later
HTML5 Gateway (on-prem) 15.2.215.2.2.0 to 15.2.2.1615.2.2.17 or later
HTML5 Gateway (on-prem) 15.0.315.0.3.0 to 15.0.3.2015.0.3.21, or 15.2.2.17 or later
Remote Access ConnectorBefore 1.1.10022021.1.1002202 or later
Remote Access Connector CLIBefore 1.1.37011.1.3701 or later

Note the PTA 15.0 row. There is no fixed build on that branch, so a 15.0 customer is looking at a version jump to 15.2.3, not a patch. Plan that as a small project with a test run and a rollback note, not a quick patch on a Friday evening.

Palo Alto says it has already fixed several cloud services on the back end: Idira EPM SaaS, Idira Remote Access, the cloud HTML5 Gateway, Prisma Access for MSPs, Prisma AIRS and ADEM infrastructure. Customers of those services have nothing to install.

How serious is this for a PAM deployment?

Palo Alto rates the flaw 9.2 (critical) under CVSS 4.0, with attack complexity marked high and its suggested urgency set to moderate. It says it is not aware of any malicious exploitation. The bug itself sits in the JVM's fast Base64 decoder on x86-64 CPUs with AVX-512 VBMI, which we covered in detail in our Java4Shell explainer.

Our judgement: the risk score is less important than where these servers sit. A privileged access system is the vault for every admin password you have. An HTML5 Gateway is often reachable from the wider network, sometimes from the internet so vendors can get in. If an attacker gets code running on that box, they are one step from your domain admin credentials. Treat these upgrades as this week's work, not next quarter's.

The advisory lists no workaround. Skip the JVM start-up flag you may have read about: editing Java settings inside a packaged PAM component can break support. Use the fixed build.

What to do, in order

  1. Confirm the firewall side and move on. Note in your change log that PAN-OS, Panorama and WF-500-B are listed as not affected, with the date.
  2. List your Idira components. Check the version of PTA, every HTML5 Gateway, every Remote Access Connector and the connector CLI. Include DR servers.
  3. Restrict access while you wait. Make sure the HTML5 Gateway and PTA are reachable only from the networks that need them, and that the gateway is not open to the internet without a reason.
  4. Upgrade gateways and connectors first, since they face users and vendors, then PTA. Get the builds through the support channel you already use for CyberArk.
  5. Check your other Java. Self-hosted Vault, PVWA, CPM and PSM are not on the list today, but Palo Alto says its investigation is still running. Recheck the advisory before you close the ticket.

What it means for CyberArk owners in India

Banks, NBFCs and insurers use PAM because their regulators push for control over privileged access, and the audit trail is part of the value. Keep a dated record of each component's version before and after, so the evidence is ready when the next RBI or IRDAI inspection asks how you handled a critical vulnerability. If you do find signs of compromise on a PAM server, CERT-In expects certain incidents to be reported within 6 hours of noticing them, so preserve logs before rebuilding anything.

Fixed builds come through your support entitlement. If your CyberArk support lapsed, or you are not sure which contract covers PTA, sort that out before the upgrade window.

Next step

We supply and support both sides of this advisory. Send us your Idira or CyberArk component list and versions, and we will map each one to its fixed build, flag anything on the unfixed PTA 15.0 branch, and plan the upgrade window. See our CyberArk (Idira) page for licences and support, or renewals if the support contract needs attention.

Questions about Java4Shell and Palo Alto products

Is PAN-OS affected by CVE-2026-114938?
No. Palo Alto says there is no impact on PAN-OS based products, including PA-Series, VM-Series and AIRS firewalls, Panorama on M-Series and VM, the WF-500-B and the PAN-DB private cloud appliance. Java tools you installed alongside the firewall yourself still need checking.
Which Idira or CyberArk versions fix Java4Shell?
Palo Alto lists Privilege Threat Analytics 15.2.3 (or 14.6.4 on the 14.6 branch), on-prem HTML5 Gateway 15.2.2.17 or 15.0.3.21, Remote Access Connector 1.1.1002202 and Remote Access Connector CLI 1.1.3701. PTA 15.0 has no fix on its own branch, so move it to 15.2.3.
Do Idira SaaS customers need to do anything?
No. Palo Alto says it has fixed Idira EPM SaaS, Idira Remote Access and the cloud HTML5 Gateway on the back end, along with Prisma Access for MSPs, Prisma AIRS and ADEM infrastructure. Self-hosted components are the ones that need your upgrade.
Is Java4Shell being exploited against Palo Alto products?
Palo Alto says it is not aware of any malicious exploitation. The flaw details are public and PAM servers hold privileged credentials, so we would still upgrade affected components this week rather than wait.

Not sure if your devices are affected? Send us the model and current firmware or version on WhatsApp, or use the form on this page. We will tell you whether this advisory applies to you and which update to schedule.

Sources

Facts in this post come from these pages, checked on 20 November 2026. Palo Alto says it will keep updating its advisory as the investigation continues, so recheck the product list before you plan the upgrade.