dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2025-61667

HIGH · 7.0 CVSS v4.0 Published 2025-11-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Datadog Agent collects events and metrics from hosts and sends them to Datadog. A vulnerability within the Datadog Linux Host Agent versions 7.65.0 through 7.70.2 exists due to insufficient permissions being set on the `opt/datadog-agent/python-scripts/__pycache__` directory during installation. Code in this directory is only run by the Agent during Agent install/upgrades. This could allow an attacker with local access to modify files in this directory, which would then subsequently be run when the Agent is upgraded, resulting in local privilege escalation. This issue requires local access to the host and a valid low privilege account to be vulnerable. Note that this vulnerability only impacts the Linux Host Agent. Other variations of the Agent including the container, kubernetes, windows host and other agents are not impacted. Version 7.71.0 contains a patch for the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Datadog Linux Host Agent (versions 7.65.0-7.70.2) sets insufficient permissions on the `opt/datadog-agent/python-scripts/__pycache__` directory during installation. A local attacker with a low-privilege account can modify Python scripts in this directory, which are executed during Agent upgrades, leading to local privilege escalation to root.

MitigationUpgrade Datadog Linux Host Agent to version 7.71.0 or later. Verify proper directory permissions after upgrade to ensure the `__pycache__` directory is not world-writable.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
Authentication
X
User interaction
P
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Datadog Agent installation
    Run `datadog-agent version` or check for the directory `/opt/datadog-agent`
    Affected if Agent is not installed means not affected by this CVE
  2. Check installed version
    Run `datadog-agent version` and compare the reported version to the affected range 7.65.0-7.70.2
    Affected if Version falls between 7.65.0 and 7.70.2 inclusive means the version is vulnerable
  3. Inspect __pycache__ directory permissions
    Run `ls -la /opt/datadog-agent/python-scripts/__pycache__` and examine the permission bits
    Affected if Directory shows world-writable permissions (the 'w' bit is set for 'others', such as 'drwxrwxrwx') means the vulnerability is present and exploitable

Your environment is affected if the Datadog Agent version is 7.65.0 through 7.70.2 AND the /opt/datadog-agent/python-scripts/__pycache__ directory is world-writable.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Datadog Linux Host Agent to version 7.71.0 or later. Verify proper directory permissions after upgrade to ensure the `__pycache__` directory is not world-writable.

Recommended fix High confidence

7.71.0 or later

  1. 1. Identify the current Datadog Agent version by running 'datadog-agent version' or checking the installed package
  2. 2. If the version is between 7.65.0 and 7.70.2 inclusive, plan for an upgrade
  3. 3. Review the Datadog Agent upgrade documentation for your installation method (package manager, ansible, puppet, etc.)
  4. 4. Before upgrading, ensure you have valid backups and can rollback if needed
  5. 5. Upgrade the Datadog Agent to version 7.71.0 or later using your deployment method
  6. 6. After upgrade, verify the new version is running with 'datadog-agent version'
  7. 7. Confirm the Agent is functioning correctly by checking status with 'datadog-agent status'
Caveat Review Datadog release notes for 7.71.0 for any potential breaking changes or deprecations specific to your configuration

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-61667 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-61667 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data