Skip to main content
Menu
CVEs

CVE

Datadog Agent local privilege escalation in SSI injector

Only affects Datadog Agent setups with Single Step Instrumentation enabled on Linux or Kubernetes while instrumenting a Java service, using datadog-apm-inject below v0.66.0. Fixed in 0.66.0.

CVE-2026-61581Published Updated Summary written by a model

7.4HighCNA
Exploited
No known exploitation
Fix
Fixed in 0.66.0
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Datadog Single Step Instrumentation (SSI) is enabled on Linux or Kubernetes At least one Java service is being instrumented via SSI datadog-apm-inject version is below v0.66.0

Summary

DataDog's datadog-agent has a local privilege escalation flaw in its Single Step Instrumentation (SSI) injector, which stores helper tooling in a predictable host directory. A local attacker with an unprivileged shell on the same Linux or Kubernetes host, where SSI is enabled and at least one Java service is instrumented, can influence that tooling and run code with the privileges of that Java service.

Original description

The Datadog Agent collects events and metrics from hosts and sends them to Datadog. Prior to datadog-apm-inject 0.66.0, the Datadog Single Step Instrumentation injector stores helper tooling in a predictable host directory. On Linux or Kubernetes systems with SSI enabled and at least one Java service instrumented through SSI, a local unprivileged attacker with shell access to the same host can influence that tooling and execute code with the privileges of the instrumented Java service. Services that use dd-java-agent without SSI and non-Java language runtimes are not affected. This issue is fixed in datadog-apm-inject 0.66.0.

Who should check

Teams running datadog-apm-inject below 0.66.0 on Linux or Kubernetes with SSI enabled and at least one Java service instrumented via SSI.

“Datadog Single Step Instrumentation (SSI) is enabled on Linux or Kubernetes”

github.com

cve.now Index

12Pcve.now Index 12 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure5/25Specific setups only
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.4/10CVSS 7.4
  • No patch0/5No signal

What would change the score

  • Would score about 62 if added to CISA KEV
  • Would score about 57 if CISA's SSVC rates exploitation active
  • Would score about 22 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    Datadog Single Step Instrumentation (SSI) is enabled on Linux or Kubernetes At least one Java service is being instrumented via SSI datadog-apm-inject version is below v0.66.0
  • Upgrade to a fixed version: 0.66.0.

  • Workaround: Ensure the host or container running Java services has no other local users with shell access.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-61581 (Datadog Agent: Datadog SSI Injector Contains Local Privilege Escalation Vulnerability), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-61581 (entry last updated 2026-11-18):
Affected:
- DataDog datadog-agent: fixed in 0.66.0
Fixed versions: 0.66.0.
Conditions (all must be true for the bug to be hit):
- Datadog Single Step Instrumentation (SSI) is enabled on Linux or Kubernetes (source: https://github.com/DataDog/datadog-agent/security/advisories/GHSA-h8qx-4jh5-pf43)
- At least one Java service is being instrumented via SSI (source: https://github.com/DataDog/datadog-agent/security/advisories/GHSA-h8qx-4jh5-pf43)
- datadog-apm-inject version is below v0.66.0 (source: https://github.com/DataDog/datadog-agent/security/advisories/GHSA-h8qx-4jh5-pf43)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, no login, no user action.
Workaround: Ensure the host or container running Java services has no other local users with shell access. (source: https://github.com/DataDog/datadog-agent/security/advisories/GHSA-h8qx-4jh5-pf43)
CISA KEV: CVE-2026-61581 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-61581 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/DataDog/datadog-agent/security/advisories/GHSA-h8qx-4jh5-pf43
- https://github.com/DataDog/datadog-agent/pull/52881
- https://github.com/DataDog/dd-apm-inject/releases/tag/v0.66.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-61581
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-61581"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • DataDog datadog-agent

    fixed in 0.66.0

Evidence 5

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · DataDog/datadog-agent · Advisory GHSA-h8qx-4jh5-pf43
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-61581
RecordNVD · CVE-2026-61581
Other links 2
RepositoryGitHub · DataDog/datadog-agent · Pull request #52881
RepositoryGitHub · DataDog/dd-apm-inject · Release v0.66.0

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-61581

Is CVE-2026-61581 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

A local user on the host can influence helper tooling kept in a predictable directory, so code runs with the privileges of the instrumented Java service process. The attacker needs local access to the machine or container.Source: github.com

Which versions are affected by CVE-2026-61581?

datadog-agent: before 0.66.0.Source: cve.now feed data

Am I affected, and how do I check?

Affected setups have Datadog Single Step Instrumentation (SSI) enabled on Linux or Kubernetes, with at least one Java service instrumented via SSI, and datadog-apm-inject below v0.66.0. Check the datadog-apm-inject version on the host or container, and check whether SSI is instrumenting any Java services.Source: github.com

How do I fix CVE-2026-61581?

Upgrade datadog-apm-inject to v0.66.0 or later, which is the fixed version. Until then, make sure the host or container running Java services has no other local users with shell access.Source: github.com

More CVEs