Palantir is a software company that builds the world's leading software for data-driven operations and decision-making. For more than a decade, we’ve worked with customers in the most secure and highly-regulated industries and built software for their most sensitive data. Today, security remains the cornerstone of our product development, company culture, and internal operations.
Palantir cares deeply about the security outcomes of our customers, and we’re committed to transparency about our security practices and program. We stand resolute in continuously improving our security, data protection, and privacy controls to give you the most effective means of protecting your data possible.
Trust and Security Portal Updates
Palantir's response to nginx CVE-2026-123633 and CVE-2026-123007
Palantir's response to nginx CVE-2026-123633 and CVE-2026-123007
November 18, 2026
Summary:
Nginx is used across a limited number of internal systems and products at Palantir. Two vulnerabilities, CVE-2026-123633 and CVE-2026-123007, could be leveraged to crash nginx or potentially execute code remotely.
Palantir is treating this as an emergency priority and is in the process of rolling out patches to our production fleet and internal services. No evidence of abuse has been found on Palantir systems.
No Palantir products deploy nginx in a public-facing, exploitable manner.
Details:
CVE-123633 affects nginx that is reverse-proxying requests and running low on connection slots. An attacker may induce that pressure. A specially crafted request can result in use-after-free in the worker process. CVE-2026-123007 does not require reverse proxying or connection-slot exhaustion. When nginx processes undisclosed traffic, a buffer overflow can be generated via the flow control window exceeding the allowed threshold.
For NGINX Open Source, patch versions 1.30.7 (stable) and 1.31.9 (mainline) mitigate this vulnerability.
Customers are advised to review and patch affected customer-managed systems.
CVE reports:
https://www.cve.org/CVERecord?id=CVE-2026-123633
https://www.cve.org/CVERecord?id=CVE-2026-123007
Nginx security advisories
https://nginx.org/en/security_advisories.html
Java vulnerability (CVE-2026-114938)
Palantir response to the Java vulnerability CVE-2026-114938
November 17, 2026
Summary:
Java is used across internal systems and Palantir products. Palantir is treating this Java vulnerability as an emergency priority and is in the process of emergency patching affected Palantir production and internal services.
Customers are strongly advised to treat remediation as an emergency priority for their own code, containers, and integrations deployed on the Palantir Platform. Palantir’s platform remediation does not replace the need to update Java runtimes bundled with customer-deployed workloads.
Details:
The issue affects processing in Java runtimes. Customers should consult their JDK provider to determine whether their runtime versions are affected and obtain patches and remediation guidance.
Customers should urgently review customer-managed systems, customer-developed integrations, and code deployed in their enrollment of the Palantir Platform. Seek patches from the relevant JDK provider, update affected Java runtimes to a provider-confirmed fixed release, rebuild affected container images, and redeploy workloads. Where patches are not yet available, follow the JDK provider’s recommended interim mitigations.
Investigation of Palantir’s production environments and internal systems is ongoing and has so far found no indications of abuse.
CVE-2026-98432
Palantir's response to CVE-2026-98432
November 5, 2026
Summary:
CVE-2026-98432 is a use-after-free race condition in the Linux kernel's IPv4 TCP handshake path. A remote, unauthenticated attacker could send crafted IPv4 TCP packets containing IP options to an affected system, potentially causing a kernel crash and denial of service.
Palantir has reviewed fleet inventory, infrastructure configuration, and ingress paths. Existing infrastructure-level controls mitigate direct exposure across the deployment paths reviewed, and Palantir has not confirmed an Internet-exploitable deployment. Validation of remaining direct-access and TCP-pass-through paths is ongoing.
Available vendor patches and additional network mitigations are being deployed across affected systems. Investigation of Palantir's production environments and internal systems is ongoing and has so far found no indications of abuse.
Details:
The vulnerability occurs when memory associated with IPv4 TCP connection handling is freed while another CPU is still using it. The published vulnerability information identifies kernel crash and denial of service as the impact. Direct data disclosure or reliable code execution has not been established.
Palantir is continuing to validate remaining exposure paths and deploy vendor patches as they become available.
Customers are strongly advised to review and apply vendor-supplied kernel updates to affected customer-managed Linux systems.
See the CVE record:
https://www.cve.org/CVERecord?id=CVE-2026-98432
See the AWS Security Bulletin:
https://aws.amazon.com/security/security-bulletins/2026-160-aws/
eMudhra Intermediate CA Private Key Issue
eMudhra Intermediate CA Private Key Exposure
October 26, 2026
Palantir response to the eMudhra intermediate CA private key exposure
Summary:
Eight eMudhra intermediate certificate authority private keys were rendered recoverable by weak key generation. The affected intermediates chain to broadly trusted roots and could be used to intercept TLS traffic from any system that continues to trust them.
Palantir is treating removal of trust in the affected intermediates as a priority remediation. Updated trust stores have been deployed across endpoints, production, and internal services.
Investigation of internal systems and Palantir production environments has found no indications of abuse.
Details:
Palantir has been tracking the disclosure that eight eMudhra intermediates were issued with keys generated by a flawed process, leaving the corresponding private keys recoverable. An attacker holding a recovered key can issue certificates that systems accept as valid, enabling machine-in-the-middle (MitM) interception. Palantir reproduced the technique against a production environment to confirm impact and validate remediation.
The updated Palantir CA bundle and associated change are complete .
Investigation of Palantir's production environments and internal systems has found no indications of abuse.
Customers are strongly advised to remove trust in the affected eMudhra intermediates from customer-managed systems, including language and runtime trust stores.
See eMudhra official statement : https://emudhra.com/en/post/certificate-security-incident
Node.js CVE-2026-111497
Palantir response to Node.js CVE-2026-111497 (Node2Shell)
Summary:
Node.js is used across internal systems and Palantir products. Node.js rates the vulnerability High, Palantir is treating remediation as an emergency priority to ensure patching is completed as soon as possible.
Node.js patched versions have been rolled out and applied across Palantir production and internal services. Investigation of internal systems and Palantir production environments has found no indications of abuse.
Details:
Palantir has been tracking the public release of exploit code (Node2Shell) targeting a Node.js vulnerability that allows remote code execution (RCE) and poses a major risk to all unpatched Node.js installations. This is a dependency vulnerability from the Brotli decoder bundled with Node.js. The decoder can be tricked into writing data past the end of a memory buffer, which is a route to crashes and potentially code execution.
Node.js has released the patched versions of 22.23.4, 24.22.1, and 26.12.1, alongside nine other vulnerabilities. Other products that bundle vulnerable Brotli code need their own vendor assessment and update. Brotli has patched this vulnerability in 1.2.1 with backports to 1.1.1 & 1.0.10.
Customers are strongly advised to review and patch affected customer-managed systems, customer-developed integrations, and customer integrated code in their enrollment of the Palantir Platform. Node.js patched versions are available in all customer-facing artifact registries, and customer container security posture is available in the Container Governance [https://www.palantir.com/docs/foundry/administration/container-governance] application. A set of upgrade assistant campaigns have been launched in-platform to help customers track their own impact; customers are strongly advised to action upgrade assistant campaigns in their environment.
See the Node.js Security Release: https://nodejs.org/en/blog/vulnerability/october-2026-security-releases


















