- Do you maintain an approved Physical Safety & Security Policy?
- Are you SOC 2 certified?
- Do you enforce Multi-Factor Authentication (MFA)?
- Do you comply with CCPA?
- Is customer data at rest encrypted with AES-256?
Risk Profile
We have secure, reliable hosting that customers can depend on. We are happy to provide details about our risk mitigation practices and recovery objectives upon request.
Trust Center Updates
Datadog’s Response to Java4Shell, a Remote Code Execution Vulnerability in OpenJDK (CVE-2026-114938)
What Happened?
On November 17, 2026, Oracle released security updates addressing CVE-2026-114938, a remote code execution vulnerability in OpenJDK with a CVSS v3.1 score of 8.1.
The vulnerability affects Java runtimes running on x86-64 CPUs that support specific instruction sets. Java runtimes on older x86-64 and ARM CPUs are not affected. Affected versions include OpenJDK 17.0.6 and later, plus the Oracle Java SE 8 performance build. For additional details, including fixed versions, review the official advisory.
What Has Datadog Done to Address This?
Datadog investigated its production and corporate environments and has applied mitigations to potentially-affected systems. We have not identified evidence of exploitation and continue to monitor the situation.
We also reviewed Datadog software that includes or runs with Java:
- Datadog Agent: No Agent update is required. The Agent is not a Java application. For JMX-based integrations, it starts a separate Java process, JMXFetch. Agent container images with JMX support (
-jmxtags) and the Agent package for Windows include OpenJDK 11, which is not affected. Other Agent images and the Agent packages for Linux and macOS do not include a Java runtime. - JMXFetch: When customers configure the Agent to use a separately installed Java runtime for JMX integrations, JMXFetch uses that runtime.
- Java tracing library: No update to
dd-trace-javais required. The library does not include a Java runtime; it runs inside the application's JVM, and applications instrumented withdd-trace-javaon affected Java runtimes and processors should apply the Java update or the interim mitigation described below.
What Do I Need to Do?
Review your environment for affected Java versions and apply the updates recommended by your Java vendor. Apply the update to all affected Java applications, as many libraries and application components can process untrusted input in a way that reaches the vulnerable code, including data received from untrusted remote servers over outbound connections. Update availability varies by Java distribution. If an update is not yet available or cannot be applied immediately, follow vendor guidance for applying any applicable mitigations.
If you use dd-trace-java, apply the Java update to the applications it instruments.
If you configured JMXFetch to use a separately installed Java runtime, check whether that runtime is affected. To identify the Java runtime JMXFetch uses, run the Agent status command and locate runtime_version in the JMX Fetch section.
If JMXFetch runs on an affected Java runtime and an update cannot be applied immediately, you can apply an interim mitigation on x86-64 hosts. On Agent 7.69 and later, add the following to datadog.yaml and restart the Agent:
jmx_java_tool_options: "-XX:+IgnoreUnrecognizedVMOptions -XX:UseAVX=2"
For earlier Agent versions, set the JAVA_TOOL_OPTIONS environment variable to the same value for the Agent service. For containerized Agents that use a custom Java runtime, you can instead set the DD_JMX_JAVA_TOOL_OPTIONS environment variable to -XX:+IgnoreUnrecognizedVMOptions -XX:UseAVX=2. If you run a FIPS-enabled Agent image, add these options to your existing JMX Java options rather than replacing them.
Use Datadog to identify exposure: App and API Protection customers can opt in to WAF rule dog-920-210 to help detect exploitation attempts. For technical details and additional detections, see the Datadog Security Labs post.
For additional assistance, contact Datadog Support.
Datadog's Response to the Node2Shell Vulnerability (CVE-2026-111497)
What Happened?
On October 27, 2026, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-111497, known as "Node2Shell," to its Known Exploited Vulnerabilities catalog. The vulnerability affects the Brotli compression library, which is bundled with Node.js and included in many other software packages, such as the Python Brotli bindings and Linux distributions that ship the Brotli library.
What Has Datadog Done to Address This?
Upon learning about the vulnerability, the Datadog Security team investigated our production environment and customer-facing software to determine where vulnerable versions of the Brotli library are in use. Datadog's publicly distributed software, including the Datadog Agent, tracing libraries, and SDKs, is not impacted, however, as we release patches, we recommend upgrading to the latest available version to reduce the risk. For the Datadog platform, our investigation has found no evidence of exploitation and has not identified any publicly exposed paths to the vulnerable components. We are rolling out updated components across our infrastructure, including updated base images and dependency updates, and will continue to monitor the situation as our remediation efforts continue.
What Do I Need to Do?
No action is required from customers with respect to Datadog products at this time. Review your own environment for affected versions of Node.js, the Python Brotli bindings, and Linux packages that include the Brotli library, and apply updates according to guidance from your vendors.
For questions regarding this vulnerability, our Support team is here to help.
Datadog's Response to PHP2Shell Vulnerabilities
What Happened?
On October 21, 2026, PHP released security updates for two critical remote code execution (RCE) vulnerabilities, CVE-2026-109618 and CVE-2026-109619. Both have a Common Vulnerability Scoring System (CVSS) v4.0 score of 9.2. The vulnerabilities are fixed in PHP 8.2.35, 8.3.36, 8.4.27, and 8.5.12. PHP 5 through PHP 8.1 are also vulnerable, but these versions are end of life and won't receive patches.
What Has Datadog Done to Address This?
Upon learning about the vulnerabilities, the Datadog Security team investigated our production and corporate surfaces to determine if we were running the vulnerable versions. After investigation, we determined that there is no impact to Datadog. The Datadog platform does not run PHP-based services. Although the Datadog APM and trace libraries do support PHP-based customer applications, these libraries themselves are not intrinsically impacted.
What Do I Need to Do?
Review your environment for affected versions of PHP and, where applicable, upgrade the underlying PHP engine to a fixed version. We released a companion blog post on Datadog Security Labs with security guidance for readers and for Datadog customers.
Datadog's Response to eMudhra Certificate Authority Compromise
What Happened?
On October 19th, Datadog became aware that eight intermediate certificate authorities operated by eMudhra (emSign) had been compromised, as disclosed by Mozilla. As a result, certificates issued by these certificate authorities can no longer be trusted. The affected certificate authorities are:
- EM EV TLS CA - G3B
- EM OV TLS CA - G3B
- EM DV TLS CA - G3B
- EM EV TLS CA - G3C
- EM OV TLS CA - G3C
- EM DV TLS CA - G3C
- EM OV CS CA - G3B
- EM OV CS CA - G3C
Additional details are available in Mozilla's incident report. Please note–this CA compromise is impacting the industry writ large and is not a Datadog-specific issue. We are responding urgently, as outlined below.
What Has Datadog Done to Address This?
We have reviewed where the compromised certificate authorities are trusted across our customer-facing software and components, as well as our internal systems, and have updated our root stores to remove compromised certificates. We have not identified any impact to customer data as a result of our investigations at this time, but we will continue to monitor the situation.
What Do I Need to Do?
Out of an abundance of caution, please review your environment for Datadog software and components that you are running (e.g., the Datadog Agent) and upgrade to the latest version. Given the scale and impact of this ecosystem-wide issue, we are pushing updates rapidly and recommend customers upgrade as quickly as possible.
For questions regarding the status of a particular Datadog component, our Support team is here to help.
*****Important: Customers Using the Datadog Agent*****
- We strongly recommend that you upgrade your fleet to the latest version of the agent
- Important: In order to remove the vulnerability, you must run agent version(s) 7.84.5 or greater (Linux) and 7.84.6 or greater (Windows). Customers running agent version(s) 6.x must upgrade to 6.53.2 or greater to remove the vulnerability
- Scanners that inventory CA bundles on disk will flag botocore/cacert.pem on 7.84.5 and 7.84.6. It is a false positive which can be avoided by upgrading to 7.85.0 or greater
- Additionally, Please Note that:
- The latest version of Helm chart (3.261.1) installs agent version 7.84.6 (safe), but it also installs Operator version 1.31.2, which defaults to version 7.84.1 (unsafe). As a workaround, you’ll need to set an override: spec.override.<component>.image.tag: 7.84.6 (where <component> is replaced by nodeAgent, clusterAgent, otelAgentGateway…). Future versions of the Operator will default to to a safe version of the agent.
- If your host uses agent v7 and cannot upgrade to a safe version of the agent, follow this runbook
- If your host uses agent v6 and you cannot upgrade to a safe 7.x version of the agent, please instead upgrade to 6.53.2
- If your host uses agent v5 and you cannot upgrade to a safe 7.x version of the agent, or 6.53.2, follow this runbook
- If your host runs the unix agent, follow this runbook
If you run into any issues when trying to upgrade, or when executing the runbooks, please reach out to our Support team.
Cyber Essentials Plus (CE+) certification
We are pleased to announce that Datadog has achieved its first Cyber Essentials Plus (CE+) certification. CE+ is a UK Government-backed certification that independently verifies an organization's protections against common cyber threats.
The certification covers Datadog's UK operations, including the UK production environment, UK-based employees, their end-user devices and associated supporting infrastructure. All other Datadog networks, locations, and infrastructure are outside the certification scope.












