* [Blog](https://www.paloaltonetworks.com/blog) * [Cloud Security](https://www.paloaltonetworks.com/blog/cloud-security/) * [Cloud Security](https://www.paloaltonetworks.com/blog/cloud-security/category/cloud-security/) * Java4Shell (CVE-2026-1149... # Java4Shell (CVE-2026-114938): Risks and Mitigations [](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fwww.paloaltonetworks.com%2Fblog%2Fcloud-security%2Fjava4shell-cve-2026-114938-risks-mitigations%2F) [](https://twitter.com/share?text=Java4Shell+%28CVE-2026-114938%29%3A+Risks+and+Mitigations&url=https%3A%2F%2Fwww.paloaltonetworks.com%2Fblog%2Fcloud-security%2Fjava4shell-cve-2026-114938-risks-mitigations%2F) [](https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fwww.paloaltonetworks.com%2Fblog%2Fcloud-security%2Fjava4shell-cve-2026-114938-risks-mitigations%2F&title=Java4Shell+%28CVE-2026-114938%29%3A+Risks+and+Mitigations&summary=&source=) [](https://www.paloaltonetworks.com//www.reddit.com/submit?url=https://www.paloaltonetworks.com/blog/cloud-security/java4shell-cve-2026-114938-risks-mitigations/&ts=markdown) \[\](mailto:?subject=Java4Shell (CVE-2026-114938): Risks and Mitigations) Link copied By [Alexandre Cezar](https://www.paloaltonetworks.com/blog/author/alexandre-cezar/?ts=markdown "Posts by Alexandre Cezar") and [Dmitry Yarushevskiy](https://www.paloaltonetworks.com/blog/author/dmitry-yarushevskiy/?ts=markdown "Posts by Dmitry Yarushevskiy") Nov 18, 2026 13 minutes [Cloud Security](https://www.paloaltonetworks.com/blog/cloud-security/category/cloud-security/?ts=markdown) [Cloud Security](https://www.paloaltonetworks.com/blog/category/cloud-security/?ts=markdown) [Threat Intelligence](https://www.paloaltonetworks.com/blog/category/threat-intelligence-1/?ts=markdown) On November 17, 2026, a memory corruption vulnerability in the OpenJDK HotSpot runtime was publicly disclosed and assigned CVE-2026-114938. The security firm Calif, which discovered the vulnerability, dubbed it "Java4Shell." The disclosure was accompanied by coordinated advisories from Oracle, the OpenJDK project, Red Hat (RHSB-2026-018) and the Canadian Centre for Cyber Security (AL26-29), along with an NVD record update. The vulnerability affects the optimized Base64 decoder used by HotSpot on modern Intel and AMD server CPUs. Servers commonly decode Base64 before authenticating users, including in HTTP Basic authentication headers, JSON Web Tokens (JWTs), SAML artifacts and file uploads. As a result, unauthenticated attackers may be able to reach the vulnerable code. Calif reports pre-authentication remote code execution (RCE) against default configurations of several widely deployed Java products. Despite its name, Java4Shell differs significantly from Log4Shell. Exploitation requires specific CPU hardware, a just-in-time (JIT)-compiled decoder and an exploit chain tailored to each target. Exploitation is sensitive to timing and network conditions, with no universal payload or confirmed exploitation in the wild at the time of writing. Java4Shell warrants prompt, prioritized patching, but it is not another Log4Shell. We strongly recommend upgrading affected Java runtimes to the fixed builds listed below, prioritizing internet-facing identity providers and DevOps platforms. Where immediate patching is not possible, apply the JVM workarounds described in this article. Research is ongoing, and we will update this post as new information becomes available. ## **What Is Java4Shell?** Java4Shell is a heap-based out-of-bounds write vulnerability in the HotSpot JVM's AVX-512 VBMI Base64 decoding intrinsic, the optimized assembly fast path behind java.util.Base64.Decoder. The vulnerability exists in the Java runtime itself, rather than in a third-party library. Distributions built from the affected OpenJDK code inherit the vulnerability. ### **How Java4Shell Works** On x86-64 CPUs supporting AVX-512 VBMI, HotSpot replaces the standard Base64 decoder with an optimized intrinsic once the method is JIT-compiled, as commonly occurs in busy services. A malformed Base64 string containing an unexpected trailing = character causes the intrinsic to miscalculate its output length. For example, 64 A characters followed by a single = can trigger the vulnerability. The decoder writes **62--63 bytes beyond the end** of its allocated output buffer on the heap. Java rejects the input as invalid, but only after the out-of-bounds write has occurred. Because the overflowing bytes are static, an attacker can control where they land, but not what is written. Early source-code analysis therefore suggested that exploitation would result in a crash rather than code execution. Researchers subsequently demonstrated RCE by shaping heap memory so the overflow expands a neighboring array. The expanded array can then be used to write arbitrary bytes, while a second array enables memory reads, a technique referred to as JavaBleed. From there, the exploit chain achieves code execution within the JVM. ![An infographic illustrating the step-by-step workflow of the Java4Shell (CVE-2026-114938) exploit based on the How it works section: Step 1 shows a server with an x86-64 CPU (AVX-512 VBMI) compiling the HotSpot Base64 decoder via JIT. Step 2 illustrates a malformed Base64 payload ending with an unexpected '=' character. Step 3 depicts the intrinsic memory buffer overflowing by 62-63 bytes out-of-bounds on the heap before Java rejects the input. Step 4 highlights memory layout shaping where static overflow bytes overlap adjacent heap structures. Step 5 demonstrates the JavaBleed technique expanding a neighboring array to achieve arbitrary read/write access and eventual remote code execution (RCE).](https://www.paloaltonetworks.com/blog/wp-content/uploads/2026/11/an-infographic-illustrating-the-step-by-step-workf.jpeg) *Image 1: CVE-2026-114938 Exploit Workflow* ## **Is Your Environment Vulnerable?** A host is exposed when all of the following conditions are met: 1. **Affected HotSpot JVM:** The host runs an affected OpenJDK-based runtime, including Java 17.0.6 through 17.0.21, Java 21 before 21.0.13.1, Java 25 before 25.0.5.1, Java 27 before 27.0.1.1, or Oracle Java SE 8u511b33-perf (Enterprise Performance Pack). End-of-life versions 18--20, 22--24 and 26 are also affected. 2. **Vulnerable CPU architecture:** The CPU is x86-64 with AVX-512 VBMI support, including Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids, or AMD Zen 4 and newer processors. AWS instance families such as c6i, m6i, c7i, c7a and m7a are among those potentially affected. 3. **Vulnerable JVM configuration:** The JVM has not been started with -XX:UseAVX=2 or -XX:-UseBASE64Intrinsics. 4. **Reachable decoding functionality:** Untrusted Base64 input reaches the basic or URL decoder, such as through authorization headers, JWTs or file uploads. 5. **JIT compilation:** The decoder has been JIT-compiled, as commonly occurs in busy services. ### **Affected Java Versions and Products** The vulnerability exists in the OpenJDK HotSpot JVM, maintained by the OpenJDK community and Oracle. Affected distributions include: | **Distribution / Runtime** | **Affected Versions** | | Oracle Java SE | 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, 27.0.1.0.3 and earlier | | Oracle GraalVM | GraalVM for JDK 17.0.21.0.3 and 21.0.13.0.3; GraalVM Enterprise 21.3.20.0.3 | | OpenJDK distributions, including Oracle OpenJDK, Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, BellSoft Liberica, SAP SapMachine and Red Hat build of OpenJDK | Java 17.0.6 through 17.0.21; Java 21 before 21.0.13.1; Java 25 before 25.0.5.1; Java 27 before 27.0.1.1 | | Linux distribution packages | Packages such as openjdk-17 before the applicable security update | |------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------| Application vendors also commonly bundle OpenJDK into their products, container base images and appliances. Examples include Jenkins, Elasticsearch, Jira, Confluence and Keycloak distributions. Products that bundle their own Java runtimes require updates from their respective vendors, even if the host's system Java installation has already been patched. ### **Available Patches and Fixed Versions** The following table summarizes fixed versions and patch availability as of November 18, 2026. | **Distribution** | **Fixed Release** | **Status** | | Oracle Java SE 8 (Performance Pack) | 8u513-perf | Available | | Oracle Java SE 17 | 17.0.21.1 | Available | | Oracle Java SE 21 | 21.0.13.1 | Available | | Oracle Java SE 25 | 25.0.5.1 | Available | | Oracle Java SE 27 | 27.0.1.1 | Available | | Oracle GraalVM | GraalVM for JDK 17.0.21.1 and 21.0.13.1; Enterprise 21.3.20.1 | Available | | Amazon Corretto | 17.0.21.1.2, 21.0.13.1.2, 25.0.5.1.2, 27.0.1.1.4 | Available | | Azul Zulu (free builds) | 17.70.201, 21.54.201, 25.38.201, 27.30.201 | Available | | SAP SapMachine | 17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1 | Released; release notes do not yet list this CVE | | Red Hat (RHEL 8/9/10, Red Hat build of OpenJDK) | Pending | Not yet available | | Eclipse Temurin, Microsoft Build of OpenJDK, BellSoft Liberica | Pending | No confirmed fix yet | | End-of-life versions (18--20, 22--24, 26) | None | Upgrade to a supported, fixed LTS version (21 or 25) | |----------------------------------------------------------------|---------------------------------------------------------------|------------------------------------------------------| ### **Environments Not Affected** The following environments are not affected by the vulnerability: | **Category** | **Details** | | Java versions | Standard Java 8 and Java 11 | | Architecture / hardware | ARM64 hosts, including AWS Graviton | | Legacy CPU features | Older x86-64 CPUs without AVX-512 VBMI | |-------------------------|----------------------------------------| **Important:** Exposure depends on the underlying CPU. The same container image may be vulnerable on one node and unaffected on another. Security teams should assess the hosts running their workloads, not just the container images. On Linux, use the following command to check whether a host's CPU supports the relevant instructions. All four flags must be present for the vulnerable CPU path to be possible: grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\\n' | grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$' ## **How Java4Shell Differs From Log4Shell** Although Java4Shell may resemble Log4Shell in its potential reach, the two vulnerabilities differ significantly in exploitability. Unlike Log4Shell, Java4Shell requires specific hardware, memory conditions and a tailored exploit chain. The following table summarizes the primary differences identified so far. | **Feature** | **Log4Shell (CVE-2021-44228)** | **Java4Shell (CVE-2026-114938)** | | Location | Logging library (Log4j 2) | JVM runtime (HotSpot Base64 intrinsic) | | Hardware dependency | None | x86-64 with AVX-512 VBMI only; ARM64 not affected | | Payload | One short string (${jndi:ldap://...}) that works wherever it is logged | Malformed Base64 combined with a target-specific memory layout and timing chain | | Universal exploit | Yes | No; each product, build and memory layout requires its own exploit chain | | Reliability | Deterministic | Timing- and network-sensitive; failed attempts often crash the JVM | | Exploitation at disclosure | Mass exploitation within hours | None confirmed; not listed in CISA KEV | | Public RCE exploit | Available within hours | Not widely available | |----------------------------|------------------------------------------------------------------------|---------------------------------------------------------------------------------| We do not expect the widespread, opportunistic internet scanning that followed the initial Log4Shell disclosure. ### **Where Java4Shell Poses the Greatest Risk** The primary concern is targeted exploitation of high-value, internet-facing Java applications. Several factors make these environments particularly important to assess: * **Widely deployed software:** Off-the-shelf products often run identical builds and memory layouts across thousands of deployments. Once an attacker develops a working exploit chain for a specific product, it may be reusable across other deployments of that product. * **AI-assisted exploit development:** AI-assisted research tools can accelerate proof-of-concept development, potentially enabling attackers to tailor exploits to specific environments, including custom-built applications. * **Publicly available triggering input:** An input capable of triggering the overflow appeared in a proposed OpenJDK pull request on September 9, 2026. The request was subsequently closed without being merged. * **High-impact targets:** Compromising a single identity provider could expose credentials, tokens and access to critical systems and pipelines across an environment. * **Denial-of-service risk:** Denial of service presents a more immediate concern. Reports indicate that approximately 28,300 malformed login requests over 20 seconds were sufficient to crash a test Spring Boot application without authentication. ### **Potential Attack Vectors** Attackers may be able to reach the vulnerable Base64 decoder through several application entry points. | **Attack Vector** | **Authentication Required** | **Examples** | | Inbound HTTP authentication data | None | Authorization: Basic ... headers, Bearer JWTs, SAML artifacts, CSRF tokens | | Inbound uploads and API payloads | Often none | Base64-encoded file uploads, attachments and API fields | | Authenticated application features | Low-privilege user | Features exposed through off-the-shelf applications | | Outbound TLS to a malicious server | None (client-side) | Java applications establishing TLS connections to attacker-controlled servers, even when the application does not expose a service | | Denial of service | None | Repeated malformed requests that crash the JVM | |------------------------------------|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------| ## **How Cortex Helps Identify and Mitigate Risk** Cortex provides capabilities to help security teams identify affected assets, assess exposure, prioritize remediation and investigate potential exploitation activity. Research is ongoing, and we continue to develop and deliver additional detection and protection mechanisms. As of November 18, 2026, PST, the following coverage is available or under active research. | **Product** | **Coverage** | **Status** | | Cortex XDR Agent | Detection of CVE-2026-114938 in Oracle Java SE on Windows and macOS | Available; OpenJDK coverage under active research | | Cortex Network Scanner | Network-based detection | Available | | Cortex Xpanse / Attack Surface Management | Attack Surface Rules (ASR) for exposed, affected services | Under active research; preliminary indicators available | |-------------------------------------------|---------------------------------------------------------------------|---------------------------------------------------------| ### **Identify Affected Assets Across Your Environment** Use the Exposure Management AI Agent to identify assets potentially affected by CVE-2026-114938, understand their exposure and prioritize remediation. The agent can help security teams investigate affected environments, add relevant risk context and gain additional insights into vulnerable assets. ![](https://www.paloaltonetworks.com/blog/wp-content/uploads/2026/11/word-image-374592-2.jpeg) *Image 2: Exposure Management AI Agent identifying CVE-2026-114938* **Find and prioritize affected endpoints** Search for CVE-2026-114938 to identify affected endpoints across your environment. Prioritize assets that are internet-exposed or have a high CVRS score to focus remediation efforts on the most significant risks. ![](https://www.paloaltonetworks.com/blog/wp-content/uploads/2026/11/word-image-374592-3.jpeg) *Image 3: Cortex vulnerability search results showing affected assets* **Access recommended remediation actions** Use Cortex Resolution Actions to access detailed remediation and mitigation guidance tailored to each vulnerability finding. ![](https://www.paloaltonetworks.com/blog/wp-content/uploads/2026/11/word-image-374592-4.jpeg) *Image 4: Cortex Resolution Actions for CVE-2026-114938* **Investigate vulnerability details** Review the Vulnerability Intelligence page for additional information about CVE-2026-114938, including its potential impact on your environment and the software affected. ![](https://www.paloaltonetworks.com/blog/wp-content/uploads/2026/11/word-image-374592-5.jpeg) *Image 5: Vulnerability Intelligence details for CVE-2026-114938* ### **Cortex XDR Detection and Protection** Cortex XDR uses a multilayered approach to help detect and protect against post-exploitation techniques, including code execution. Security teams can also use the Cortex XDR agent's remote script execution capability to run detection scripts. Additional XQL-based queries for threat hunting and post-exploitation investigation are available in the[Cortex XDR detection resources](https://snippets.gocortex.io/snippet/202611172208). ### **Identify Internet-Exposed Assets with Cortex Xpanse** Attack Surface Rules (ASR) for internet-exposed services running affected Java runtimes are currently under active research. In the meantime, use your existing attack surface inventory to identify exposed Keycloak, PingFederate, Jira, Confluence, Jenkins and Artifactory instances. Prioritize these assets for patching based on their exposure and criticality. ### **Identify and Remediate Vulnerabilities with Cortex Cloud** Cortex Cloud helps security teams identify vulnerabilities in container images and application components earlier in the development lifecycle. Through code-to-cloud tracing, teams can connect vulnerable software to deployed workloads, identify the source repositories and teams responsible, and prioritize remediation based on cloud and runtime context. Developers can then address affected components at the source and help prevent vulnerable images from being redeployed. ## **Recommended Remediation and Mitigation Steps** Security teams should prioritize patching vulnerable Java runtimes, starting with internet-facing applications and critical infrastructure. When patches are not immediately available, apply the recommended JVM workarounds and additional risk reduction measures. ### **Remediation** To remediate CVE-2026-114938: 1. Install Oracle's fixed Java builds or the applicable fixed release from your Java distribution vendor. 2. Update applications that bundle their own JDK through the respective product vendor. 3. Restart affected JVMs, and rebuild and redeploy container images to ensure the updated runtime is in use. 4. Verify the version of each running Java process to confirm that the fixed build has been applied. Updating a package on disk does not protect JVM processes that have not been restarted. ### **Workarounds** If immediate patching is not possible, start affected JVMs with one of the following flags. Remove the workaround after installing the fixed build. | **JVM Flag** | **Effect** | **Considerations** | | -XX:-UseBASE64Intrinsics (recommended) | Disables only the optimized Base64 code, removing the vulnerable execution path | Workloads performing extensive Base64 decoding may experience reduced performance | | -XX:UseAVX=2 | Disables AVX-512 entirely | Applies only to x86-64. On ARM64, the JVM does not recognize the flag and will not start. May have a broader performance impact | |----------------------------------------|---------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------| **Warning:** Do not use -XX:DisableIntrinsic=\_base64\_decodeBlock on its own. Reports indicate that the flag can prevent the JVM from starting. ### **Additional Risk Reduction Measures** Organizations should consider the following measures while applying patches: * **Restrict exposure:** Temporarily limit public access to vulnerable management applications until they are patched. * **Review reverse proxy configurations:** A reverse proxy that buffers complete requests, such as nginx in its default configuration, may block some exploit chains but does not provide comprehensive protection. * **Apply NGFW and WAF protections:** Network security controls can help defend against specific exploit techniques as protections become available. ### **Prioritize High-Risk Environments** Because exploitation requires a chain tailored to each target, remediation should prioritize systems where successful compromise could have the greatest impact. We recommend the following order: 1. Internet-facing identity providers 2. Critical infrastructure 3. Other internet-facing Java services handling authentication, tokens or uploads 4. Java clients connecting to untrusted external TLS endpoints 5. Internal Java services 6. Remaining affected environments ### **Indicators of Potential Exploitation** Security teams should monitor for potential signs of exploitation attempts, including: * Base64 tokens of 32 characters or more that end in = and have a length that is not a multiple of four, particularly in Authorization headers. * Bursts of IllegalArgumentException errors from java.util.Base64$Decoder. * Unexplained hs\_err\_pid\*.log JVM crash files or repeated service restarts. These indicators may suggest exploitation attempts but do not independently confirm a compromise. Their absence also does not establish that a host is safe. ## **Key Takeaways** Java4Shell (CVE-2026-114938) is a serious memory corruption vulnerability in the Java runtime that can lead to pre-authentication remote code execution under specific conditions. Widely deployed applications such as Keycloak, Jira, Confluence and Jenkins may be exposed when running affected Java runtimes on vulnerable hardware. Unlike Log4Shell, exploitation requires specific x86-64 hardware, a JIT-compiled decoder and a timing-sensitive exploit chain tailored to the target. No universal exploit has been identified, and successful exploitation in the wild had not been confirmed at the time of writing. Security teams should treat Java4Shell as a high-priority, targeted risk. Identify affected runtimes, prioritize patching internet-facing applications and critical infrastructure, and apply available workarounds where immediate patching is not possible. Restart JVMs and rebuild container images to ensure updated runtimes are running. ## **Identify and Remediate Vulnerabilities with Cortex** Cortex helps security teams identify affected assets, prioritize vulnerabilities based on risk and investigate potential threats across their environments. [Request a demo](https://www.paloaltonetworks.com/cortex/request-demo?ts=markdown) to see how Cortex can help you identify exposure and accelerate remediation. *** ** * ** *** ## Related Blogs ### [AppSec](https://www.paloaltonetworks.com/blog/cloud-security/category/appsec/?ts=markdown), [Cloud Security](https://www.paloaltonetworks.com/blog/cloud-security/category/cloud-security/?ts=markdown), [Cloud Security](https://www.paloaltonetworks.com/blog/category/cloud-security/?ts=markdown), [Software Supply Chain Security](https://www.paloaltonetworks.com/blog/cloud-security/category/software-supply-chain-security/?ts=markdown), [Vulnerability Management](https://www.paloaltonetworks.com/blog/cloud-security/category/vulnerability-management/?ts=markdown) [#### How Cortex Cloud Protects Against PHP2Shell Vulnerabilities From Code to Cloud](https://www.paloaltonetworks.com/blog/cloud-security/how-cortex-cloud-protects-against-php2shell-vulnerabilities-from-code-to-cloud/) ### [Cloud Security](https://www.paloaltonetworks.com/blog/category/cloud-security/?ts=markdown), [Threat Intelligence](https://www.paloaltonetworks.com/blog/category/threat-intelligence-1/?ts=markdown), [Unit 42](https://unit42.paloaltonetworks.com) [#### When Security Scanners Become the Weapon: Breaking Down the Trivy Supply Chain Attack](https://www.paloaltonetworks.com/blog/cloud-security/trivy-supply-chain-attack/) ### [Announcement](https://www.paloaltonetworks.com/blog/category/announcement/?ts=markdown), [Cloud Security](https://www.paloaltonetworks.com/blog/cloud-security/category/cloud-security/?ts=markdown), [CNAPP](https://www.paloaltonetworks.com/blog/cloud-security/category/cnapp/?ts=markdown), [Products and Services](https://www.paloaltonetworks.com/blog/category/products-and-services/?ts=markdown), [Threat Intelligence](https://www.paloaltonetworks.com/blog/category/threat-intelligence-1/?ts=markdown) [#### Where Cloud Security Stands Today and Where AI Breaks It](https://www.paloaltonetworks.com/blog/2025/12/cloud-security-2025-report-insights/) ### [Cloud Security](https://www.paloaltonetworks.com/blog/category/cloud-security/?ts=markdown), [Threat Intelligence](https://www.paloaltonetworks.com/blog/category/threat-intelligence-1/?ts=markdown), [Unit 42](https://unit42.paloaltonetworks.com) [#### Closing the Cloud Security Gap](https://www.paloaltonetworks.com/blog/2025/10/closing-the-cloud-security-gap/) ### [Cloud Security](https://www.paloaltonetworks.com/blog/cloud-security/category/cloud-security/?ts=markdown), [Threat Intelligence](https://www.paloaltonetworks.com/blog/category/threat-intelligence-1/?ts=markdown) [#### Critical Vulnerability in Confluence Data Center and Server CVE-2023-22515](https://www.paloaltonetworks.com/blog/cloud-security/confluence-unauthenticated-critical-vulnerability-2023/) ### [CIEM](https://www.paloaltonetworks.com/blog/cloud-security/category/ciem/?ts=markdown), [Cloud Security](https://www.paloaltonetworks.com/blog/cloud-security/category/cloud-security/?ts=markdown), [Cloud Security](https://www.paloaltonetworks.com/blog/category/cloud-security/?ts=markdown), [IAM](https://www.paloaltonetworks.com/blog/cloud-security/category/iam/?ts=markdown), [Points of View](https://www.paloaltonetworks.com/blog/category/points-of-view/?ts=markdown) [#### Why Are Net-Effective Permissions Critical for Cloud IAM?](https://www.paloaltonetworks.com/blog/cloud-security/net-effective-permissions-iam/) ### Subscribe to Cloud Security Blogs! Sign up to receive must-read articles, Playbooks of the Week, new feature announcements, and more. ![spinner](https://www.paloaltonetworks.com/blog/wp-content/themes/panwblog2023/dist/images/ajax-loader.gif) Sign up Please enter a valid email. By submitting this form, you agree to our [Terms of Use](https://www.paloaltonetworks.com/legal-notices/terms-of-use?ts=markdown) and acknowledge our [Privacy Statement](https://www.paloaltonetworks.com/legal-notices/privacy?ts=markdown). Please look for a confirmation email from us. If you don't receive it in the next 10 minutes, please check your spam folder. This site is protected by reCAPTCHA and the Google [Privacy Policy](https://policies.google.com/privacy) and [Terms of Service](https://policies.google.com/terms) apply. {#footer} {#footer} Products and Services * [AI-Powered Network Security Platform](https://www.paloaltonetworks.com/network-security?ts=markdown) * [Secure AI by Design](https://www.paloaltonetworks.com/ai-security?ts=markdown) * [Prisma AIRS](https://www.paloaltonetworks.com/ai-security/prisma-airs?ts=markdown) * [AI Access Security](https://www.paloaltonetworks.com/sase/ai-access-security?ts=markdown) * [Cloud Delivered Security Services](https://www.paloaltonetworks.com/network-security/security-subscriptions?ts=markdown) * [Advanced Threat Prevention](https://www.paloaltonetworks.com/network-security/advanced-threat-prevention?ts=markdown) * [Advanced URL Filtering](https://www.paloaltonetworks.com/network-security/advanced-url-filtering?ts=markdown) * [Advanced WildFire](https://www.paloaltonetworks.com/network-security/advanced-wildfire?ts=markdown) * [Advanced DNS Security](https://www.paloaltonetworks.com/network-security/advanced-dns-security?ts=markdown) * [Enterprise Data Loss Prevention](https://www.paloaltonetworks.com/sase/enterprise-data-loss-prevention?ts=markdown) * [Enterprise IoT Security](https://www.paloaltonetworks.com/network-security/enterprise-device-security?ts=markdown) * [Medical IoT Security](https://www.paloaltonetworks.com/network-security/medical-device-security?ts=markdown) * [Industrial OT Security](https://www.paloaltonetworks.com/network-security/ot-security-solution?ts=markdown) * [SaaS Security](https://www.paloaltonetworks.com/sase/saas-security?ts=markdown) * [Next-Generation Firewalls](https://www.paloaltonetworks.com/network-security/next-generation-firewall?ts=markdown) * [Hardware Firewalls](https://www.paloaltonetworks.com/network-security/hardware-firewall-innovations?ts=markdown) * [Software Firewalls](https://www.paloaltonetworks.com/network-security/software-firewalls?ts=markdown) * [Strata Cloud Manager](https://www.paloaltonetworks.com/network-security/strata-cloud-manager?ts=markdown) * [SD-WAN for NGFW](https://www.paloaltonetworks.com/network-security/sd-wan-subscription?ts=markdown) * [PAN-OS](https://www.paloaltonetworks.com/network-security/pan-os?ts=markdown) * [Panorama](https://www.paloaltonetworks.com/network-security/panorama?ts=markdown) * [Secure Access Service Edge](https://www.paloaltonetworks.com/sase?ts=markdown) * [Prisma SASE](https://www.paloaltonetworks.com/sase?ts=markdown) * [Application Acceleration](https://www.paloaltonetworks.com/sase/app-acceleration?ts=markdown) * [Autonomous Digital Experience Management](https://www.paloaltonetworks.com/sase/adem?ts=markdown) * [Enterprise DLP](https://www.paloaltonetworks.com/sase/enterprise-data-loss-prevention?ts=markdown) * [Prisma Access](https://www.paloaltonetworks.com/sase/access?ts=markdown) * [Prisma Browser](https://www.paloaltonetworks.com/sase/prisma-browser?ts=markdown) * [Prisma SD-WAN](https://www.paloaltonetworks.com/sase/sd-wan?ts=markdown) * [Remote Browser Isolation](https://www.paloaltonetworks.com/sase/remote-browser-isolation?ts=markdown) * [SaaS Security](https://www.paloaltonetworks.com/sase/saas-security?ts=markdown) * [AI-Driven Security Operations Platform](https://www.paloaltonetworks.com/cortex?ts=markdown) * [Cloud Security](https://www.paloaltonetworks.com/cortex/cloud?ts=markdown) * [Cortex Cloud](https://www.paloaltonetworks.com/cortex/cloud?ts=markdown) * [Application Security](https://www.paloaltonetworks.com/cortex/cloud/application-security?ts=markdown) * [Cloud Posture Security](https://www.paloaltonetworks.com/cortex/cloud/cloud-posture-security?ts=markdown) * [Cloud Runtime Security](https://www.paloaltonetworks.com/cortex/cloud/runtime-security?ts=markdown) * [Prisma Cloud](https://www.paloaltonetworks.com/prisma/cloud?ts=markdown) * [AI-Driven SOC](https://www.paloaltonetworks.com/cortex?ts=markdown) * [Cortex XSIAM](https://www.paloaltonetworks.com/cortex/cortex-xsiam?ts=markdown) * [Cortex XDR](https://www.paloaltonetworks.com/cortex/cortex-xdr?ts=markdown) * [Cortex XSOAR](https://www.paloaltonetworks.com/cortex/cortex-xsoar?ts=markdown) * [Cortex Xpanse](https://www.paloaltonetworks.com/cortex/cortex-xpanse?ts=markdown) * [Unit 42 Managed Detection \& Response](https://www.paloaltonetworks.com/unit42/respond/managed-detection-response?ts=markdown) * [Managed XSIAM](https://www.paloaltonetworks.com/cortex/managed-xsiam?ts=markdown) * Observability * [Cortex XCOR](https://www.paloaltonetworks.com/cortex/xcor?ts=markdown) * [Next-Generation Identity Security](https://www.paloaltonetworks.com/idira?ts=markdown) * [Privileged Access Management](https://www.paloaltonetworks.com/idira/human/privileged-access-management?ts=markdown) * [Identity and Access Management](https://www.paloaltonetworks.com/idira/human/identity-and-access-management?ts=markdown) * [Endpoint Privilege Manager](https://www.paloaltonetworks.com/idira/human/endpoint-privilege-manager?ts=markdown) * [Identity Governance](https://www.paloaltonetworks.com/idira/human/identity-governance?ts=markdown) * [Workforce Password Management](https://www.paloaltonetworks.com/idira/human/workforce-password-management?ts=markdown) * [Agentic Identities](https://www.paloaltonetworks.com/idira/agentic?ts=markdown) * [Secrets Management](https://www.paloaltonetworks.com/idira/machine/secrets-management?ts=markdown) * [Unified Secrets Governance](https://www.paloaltonetworks.com/idira/machine/unified-secrets-governance?ts=markdown) * [Application Credentials Delivery](https://www.paloaltonetworks.com/idira/machine/application-credentials-delivery?ts=markdown) * [Vendor Privileged Access](https://www.paloaltonetworks.com/idira/human/vendor-privileged-access?ts=markdown) * [Threat Intel and Incident Response Services](https://www.paloaltonetworks.com/unit42?ts=markdown) * [Prepare for Emerging Risks](https://www.paloaltonetworks.com/unit42/prepare-for-emerging-risks/continuous-frontier-ai-defense?ts=markdown) * [Strengthen Your Defenses](https://www.paloaltonetworks.com/unit42/strengthen-your-defenses?ts=markdown) * [Build Your Security Strategy](https://www.paloaltonetworks.com/unit42/build-your-security-strategy?ts=markdown) * [Understand the Adversary](https://www.paloaltonetworks.com/unit42/threat-intelligence?ts=markdown) * [Respond to a Cyber Attack](https://www.paloaltonetworks.com/unit42/respond?ts=markdown) Company * [About Us](https://www.paloaltonetworks.com/about-us?ts=markdown) * [Careers](https://jobs.paloaltonetworks.com/en/) * [Contact Us](https://www.paloaltonetworks.com/company/contact-sales?ts=markdown) * [Corporate Responsibility](https://www.paloaltonetworks.com/about-us/corporate-responsibility?ts=markdown) * [Customers](https://www.paloaltonetworks.com/customers?ts=markdown) * [Investor Relations](https://investors.paloaltonetworks.com/) * [Location](https://www.paloaltonetworks.com/about-us/locations?ts=markdown) * [Newsroom](https://www.paloaltonetworks.com/company/newsroom?ts=markdown) Popular Links * [Blog](https://www.paloaltonetworks.com/blog/?ts=markdown) * [Communities](https://www.paloaltonetworks.com/communities?ts=markdown) * [Content Library](https://www.paloaltonetworks.com/resources?ts=markdown) * [Cyberpedia](https://www.paloaltonetworks.com/cyberpedia?ts=markdown) * [Event Center](https://events.paloaltonetworks.com/) * [Manage Email Preferences](https://start.paloaltonetworks.com/preference-center) * [Products A-Z](https://www.paloaltonetworks.com/products/products-a-z?ts=markdown) * [Product Certifications](https://www.paloaltonetworks.com/legal-notices/trust-center/certifications?ts=markdown) * [Report a Vulnerability](https://www.paloaltonetworks.com/security-disclosure?ts=markdown) * [Sitemap](https://www.paloaltonetworks.com/sitemap?ts=markdown) * [Tech Docs](https://docs.paloaltonetworks.com/) * [Unit 42](https://unit42.paloaltonetworks.com/) * [Do Not Sell or Share My Personal Information](https://panwedd.exterro.net/portal/dsar.htm?target=panwedd) ![Palo Alto Networks Logo](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/pan-logo-dark.svg) * [Privacy](https://www.paloaltonetworks.com/legal-notices/privacy?ts=markdown) * [Trust Center](https://www.paloaltonetworks.com/legal-notices/trust-center?ts=markdown) * [Terms of Use](https://www.paloaltonetworks.com/legal-notices/terms-of-use?ts=markdown) * [Documents](https://www.paloaltonetworks.com/legal?ts=markdown) Copyright © 2026 Palo Alto Networks. All Rights Reserved * [![Youtube](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/social/youtube-black.svg)](https://www.youtube.com/user/paloaltonetworks) * [![Podcast](https://www.paloaltonetworks.com/content/dam/pan/en_US/images/icons/podcast.svg)](https://www.paloaltonetworks.com/podcasts/threat-vector?ts=markdown) * [![Facebook](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/social/facebook-black.svg)](https://www.facebook.com/PaloAltoNetworks/) * [![LinkedIn](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/social/linkedin-black.svg)](https://www.linkedin.com/company/palo-alto-networks) * [![Twitter](https://www.paloaltonetworks.com/etc/clientlibs/clean/imgs/social/twitter-x-black.svg)](https://twitter.com/PaloAltoNtwks) * EN Select your language