CVE-2025-30641
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 · uneditedA link following vulnerability in the anti-malware solution portion of 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 confidenceA link following (symlink) vulnerability in the anti-malware component of Trend Micro Deep Security 20.0 agents allows a local attacker with low-privileged code execution to escalate to higher privileges by manipulating symbolic links that the privileged service follows.
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< 20.0.1= 20.0.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Deep Security Agent is installedLocate the Deep Security Agent on the system. On Windows, check for the ds_agent service in Services or the installation path under Program Files. On Linux, check for /opt/ds_agent directory or run 'ds_agent --version' if the binary exists.Affected if The Deep Security Agent is not present on the system
-
Determine the installed agent versionRetrieve the exact version of the installed Deep Security Agent. On Windows, right-click ds_agent.exe, select Properties, and check the File Version. On Linux, run 'ds_agent --version' or inspect the version file in the agent directory.Affected if Version is less than 20.0.1 (such as 20.0.0, 12.x, etc.) or equals exactly 20.0.1
-
Confirm anti-malware component is enabledCheck if the anti-malware feature of the Deep Security Agent is active. This can be verified through the Deep Security console policy settings, or by querying the agent status via command line if available.Affected if The anti-malware module is enabled and running on the agent
The system is affected if Deep Security Agent version is less than 20.0.1 or equals 20.0.1 and the anti-malware component is enabled, allowing a low-privileged local attacker to potentially escalate privileges via symlink manipulation.
Generated from the published advisory. Verify against your own configuration.
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 · scoped20.0.1
Apply the vendor patch or update to Deep Security 20.0 agents as soon as feasible; ensure least-privilege principles are maintained and monitor for suspicious symbolic link creation in agent directories.
Any Deep Security Agent version higher than 20.0.1 (e.g., 20.0.2 or later) - verify the specific fixed version in Trend Micro security bulletin
- 1. Identify the current Deep Security Agent version installed on affected systems using the agent status command or system inventory.
- 2. Download the latest Deep Security Agent version from the Trend Micro download center or your licensed software distribution point.
- 3. Test the upgrade in a non-production environment first to verify compatibility with your operating system and other security products.
- 4. Deploy the upgrade to production systems using your standard deployment method (manual install, push via manager, or automation tool).
- 5. Verify the agent version has been successfully upgraded and is communicating with the Deep Security Manager.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30641 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-30641 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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