How severe is CVE-2021-21331?

CVE-2021-21331 has a CVSS score of 3.3/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2021-21331?

CVE-2021-21331 affects the following packages: com.datadoghq:datadog-api-client (Maven). Ecosystems affected: Maven.

How do I fix CVE-2021-21331?

Update com.datadoghq:datadog-api-client to 1.0.0-beta.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-21331 is resolved across your whole dependency graph.

How do I detect CVE-2021-21331 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.datadoghq:datadog-api-client, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2021-21331 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2021-21331 actively exploited in the wild?

No public exploit code has been indexed for CVE-2021-21331 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2021-21331?

CVE-2021-21331 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 48th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2021-21331?

CVE-2021-21331 is classified as CWE-378 (CWE-378), CWE-379 (CWE-379). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2021-21331 published, and has it been updated?

CVE-2021-21331 was published on March 3, 2021 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

LOW severity

CVE-2021-21331 — datadog-api-client

LOW

CVE-2021-21331 is a low-severity (CVSS 3.3) CWE-378 vulnerability in com.datadoghq:datadog-api-client. A fix is available for com.datadoghq:datadog-api-client — see the affected versions and patch details below.

Local Information Disclosure Vulnerability

Also known asGHSA-2cxf-6567-7pp6

Published

Mar 3, 2021

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs48th percentile — riskier than 48% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2021-21331 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

☕com.datadoghq:datadog-api-client

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Local information disclosure of sensitive information downloaded via the API using the API Client.

Finding

The Datadog API is executed on a unix-like system with multiple users. The API is used to download a file containing sensitive information. This sensitive information is exposed locally to other users. This vulnerability exists in the API Client for version 1 and 2. The method prepareDownloadFilecreates creates a temporary file with the permissions bits of -rw-r--r-- on unix-like systems. On unix-like systems, the system temporary directory is shared between users. As such, the contents of the file downloaded via the downloadFileFromResponse method will be visible to all other users on the local system.

Analysis of the finding determined that the affected code was unused, meaning that the exploitation likelihood is low. The unused code has been removed, effectively mitigating this issue.

This vulnerability was found due to this query that Jonathan Leitschuh contributed to the Semmle QL project.

Patches

This issue has been patched in version 1.0.0-beta.9.

Workarounds

The recommended workaround is to specify java.io.tmpdir when starting the JVM with the flag -Djava.io.tmpdir, specifying a path to a directory with drw------- permissions owned by dd-agent.

References

For more information

If you have any questions or comments about this advisory:

Open an issue in DataDog/datadog-api-client-java
Email us at [email protected]

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.datadoghq:datadog-api-client`	≥ 1.0.0-beta.6&&< 1.0.0-beta.9	1.0.0-beta.9`com.datadoghq:datadog-api-client:1.0.0-beta.9`

Affected Products

1 product · 8 configurations

Application

datadog-api-client-javadatadoghq

1 version

1.0.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.datadoghq:datadog-api-client, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.datadoghq:datadog-api-client to 1.0.0-beta.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-21331 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

### Impact Local information disclosure of sensitive information downloaded via the API using the API Client. ### Finding The Datadog API is executed on a unix-like system with multiple users. The API is used to download a file containing sensitive information. This sensitive information is exposed locally to other users. This vulnerability exists in the API Client for version 1 and 2. The method `prepareDownloadFilecreates` creates a temporary file with the permissions bits of `-rw-r--r--` on unix-like systems. On unix-like systems, the system temporary directory is shared between users. As