Intel

AIKIDO-2026-961466

dd-trace is vulnerable to Cleartext Transmission of Sensitive Information

Cleartext Transmission of Sensitive Information Pre-CVE
Found by Aikido Intel before public disclosure or CVE publication.
Published Today

59

Medium Risk

This Affects:

JSdd-trace
5.88.0 - 5.106.0
Fixed in 5.107.0
Are you affected? Scan for Free

TL;DR

The dd-trace agentless exporter and shared HTTP request helper can place the Datadog API key on plain HTTP connections to non-loopback hosts when agentless intake is configured or a cleartext intake URL is inherited from agent settings. Affected versions also include sensitive configuration values such as DD_API_KEY, DD_APP_KEY, and OTLP header maps in library configuration telemetry. An on-path network observer or unintended telemetry recipient could read these credentials before the fix. The patch forces agentless intake over HTTPS, strips API-key headers from non-loopback cleartext requests, and omits sensitive configuration entries from telemetry.

Who does this affect?

You are affected if you are using a version that falls within the vulnerable range and you use agentless span intake with DD_API_KEY or exporter paths that can send the Datadog API key over plain HTTP to non-loopback hosts.

Background info

dd-trace is vulnerable to Cleartext Transmission of Sensitive Information in versions 5.88.0 - 5.106.0.

How to fix this

Upgrade the dd-trace library to the patch version.