Drata Response to Java4Shell (CVE-2026-114938)
Drata Logo

Trust Center

Start your security review
View & download sensitive information
ControlK

SafeBase helps B2B SaaS companies close enterprise deals faster by streamlining the security assessment process. We take security seriously and have a dedicated internal security team. Our security team's controls and policies are detailed in this Trust Center. If you have any additional questions or concerns, please email us at security@drata.com.

  • OpenAI
  • LinkedIn
  • Abnormal Security
  • Asana
  • Wiz
  • Instacart
  • ClickUp
  • Zoom
  • Ramp
  • Crossbeam
  • GitLab
  • T-Mobile
  • Jamf
  • Palantir

Documents

REPORTSHIPAA Report
Knowledge Base (FAQ)
  • What is Drata's tenancy model and how is customer data segregated?
  • Will my data be transferred or shared with any third parties?
  • Are there any web facing application protection mechanisms?
  • Does Drata maintain a risk management program, perform risk assessments, and track the treatment of those risks?
  • Do all users have unique ID's for access to production systems and data?
View more

Trust Center Updates

Drata Response to Java4Shell (CVE-2026-114938)

Vulnerabilities

Drata does not use Java within the Drata Trust Management Platform, and our production infrastructure is not affected by this vulnerability. We are monitoring our vendors for any impacts and will take measures as appropriate to secure Drata and our customers.

Drata Response to the eMudhra certificate authority compromise

Vulnerabilities

On October 20, 2026, the private keys for eight intermediate certificate authorities (CAs) operated by eMudhra were weak enough to be recovered from their public certificates. Anyone with access to these keys could potentially issue fraudulent certificates for websites to potentially intercept or alter encrypted traffic from systems that still trust the affected CAs. eMudhra has since revoked these certificates, major browser and operating system vendors have blocked the use of these certificates, and related fixes to affected software are tracked as CVE-2026-111943.
Drata does not use any eMudhra-issued certificates. To confirm any exposure, Drata’s Security and Engineering teams reviewed certificate trust across our environment and have removed any affected CAs from the trusted certificate bundles used by Drata. We have not identified evidence of exploitation affecting Drata or our customers. We are updating remaining lower-risk internal components as part of our standard vulnerability management process and continue to monitor our environment.

Drata Response to Node.js vulnerabilities

Vulnerabilities

On October 21, 2026, details of several high-severity vulnerabilities in the Node.js runtime, including CVE-2026-111497 (known as “Node2Shell”), were made public.
Drata’s Security team has assessed the impact of these vulnerabilities on Drata and, as of October 23, 2026, we have patched any impacted production services. We have not identified any evidence of exploitation affecting Drata or our customers. We are updating a few remaining components with lower-severity impacts (in accordance with our standard vulnerability management process) and will continue to monitor our environment.

Drata Not Impacted by PHP2Shell Vulnerabilities

Vulnerabilities

On October 21, 2026, Drata became aware of the PHP2Shell security vulnerabilities. Reputable threat intelligence sources have reported that these vulnerabilities affect the core PHP language runtime and could allow unauthenticated remote code execution on web servers running vulnerable PHP versions (CVE-2026-109618, CVE-2026-109619).


We want our customers to know that Drata is not impacted by this vulnerability.


Our investigation supports this assessment:

  • PHP is not part of the Drata or SafeBase platforms. Our products are built mainly on TypeScript, Python and Go. No production service or customer-facing system runs PHP, and no subprocessors have disclosed being impacted at the time of this update.
  • No internet-exposed vulnerable assets. Our cloud security platform found no vulnerable PHP on any internet-facing or production workload.
  • Limited, non-exploitable presence in build tooling. PHP was present only as a preinstalled package on 1 internal ephemeral service. There it does not serve web requests and accepts no inbound network traffic. Even so, we have applied the patched packages. 

The confidentiality, integrity and availability of the Drata product and customer data remain unharmed.

We will continue to monitor the situation and will update this post if additional information materially changes this assessment. If you have questions, please contact security@drata.com.

May 2026 TanStack Mini Shai-Hulud Supply Chain Attack Assessment

Incidents

On May 11, 2026, Drata became aware of the TanStack Mini Shai-Hulud supply chain attack security incident. Reputable threat intelligence sources have reported that this incident compromised 84 packages in the @tanstack/* npm namespace, modifying affected versions to steal CI/CD credentials and exfiltrate data to attacker-controlled infrastructure.

We leverage TanStack packages within our product, but our pinned versions predate the affected range. We conducted a thorough investigation including cross-referencing our dependencies against the confirmed compromised package list, scanning our codebases and developer endpoint environments for malicious files associated with this campaign, and searching our endpoint and network telemetry for known attacker infrastructure. At this time, based on our analysis and investigation, we have not found indications of compromise.

If you need help using this Trust Center, please contact us.
Contact support
If you think you may have discovered a vulnerability, please send us a note.
Report issue