dbcve.org
Deep Security AgentApplication · Trendmicro

CVE-2025-30640

HIGH · 7.8 CVSS v3.1 Published 2025-06-17
Fix available
A fix is available. Upgrade to 20.0.1 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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
A link following vulnerability in Trend Micro Deep Security 20.0 agents could allow a local attacker to escalate privileges on affected installations. Please note: an attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability.

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 · moderate confidence

This is a link following (symlink attack) vulnerability in Trend Micro Deep Security 20.0 agents that allows a local attacker with low-privileged code execution to escalate to higher privileges. The vulnerability stems from the agent following symbolic links without proper validation, enabling manipulation of file system operations to gain unauthorized access.

MitigationApply the vendor-provided patch when released by Trend Micro. Until then, restrict file system access to the Deep Security agent directories and monitor for suspicious symlink creation in agent-controlled directories.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Deep Security AgentApplication
Affected:< 20.0.1= 20.0.1

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
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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. Identify Deep Security Agent installation and version
    Locate the Deep Security Agent installation directory and find the version information. On Windows, this is typically in Program Files or Program Files (x86)\Trend Micro\Deep Security Agent. Look for a version file or check agent service properties.
    Affected if Installed version is less than 20.0.1 or exactly equals 20.0.1
  2. Verify symlink creation capability in agent directories
    Check file system permissions on the Deep Security Agent installation directories. Determine if low-privileged users can create new files, including symbolic links, within agent-controlled directories.
    Affected if Low-privileged users have write/create permissions to agent directories, allowing symlink injection
  3. Inspect agent directories for existing symlinks
    List all symbolic links within the Deep Security Agent directories and subdirectories. Use commands like 'dir /AL' on Windows or 'ls -la' to identify any symbolic links present in agent-controlled paths.
    Affected if Unexpected or unauthorized symbolic links exist in agent directories
  4. Review file system audit logs for symlink creation
    Examine security/event logs for file system audit events related to symbolic link creation in Deep Security Agent directories. Look for Event ID 4663 or equivalent audit events indicating symlink operations.
    Affected if Recent symlink creation events are found in agent directories without corresponding legitimate agent operations

A system is affected if Deep Security Agent version is 20.0.1 or lower AND low-privileged users can create symbolic links within agent-controlled directories.

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
Upgrade available Upgrade to 20.0.1 or later
Fixed in 20.0.1
Interim mitigation

Apply the vendor-provided patch when released by Trend Micro. Until then, restrict file system access to the Deep Security agent directories and monitor for suspicious symlink creation in agent-controlled directories.

Recommended fix Moderate confidence

Deep Security Agent 20.0.1 or later

  1. 1. Verify the current Deep Security Agent version installed on the target system using the appropriate package manager or system inventory tool
  2. 2. Download the Deep Security Agent version 20.0.1 or later from the official Trend Micro download center or your licensed software repository
  3. 3. Backup current agent configuration and policy settings before upgrading
  4. 4. Upgrade the Deep Security Agent package using the system's package manager (e.g., rpm, dpkg, or the agent's native installer)
  5. 5. Verify the upgrade completed successfully and the agent is communicating with the Deep Security Manager
  6. 6. Confirm the agent is running with the updated version

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

Fix this in Deep Security Agent Scoped from the published advisory
  • Consultation4.0 h
  • Review / QA2.0 h
6.0 hours of engineering $1,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-30640 — 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-30640 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