dbcve.org
Trend Micro Endpoint EncryptionApplication · Trendmicro

CVE-2025-49217

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-17
Fix available
A fix is available. Upgrade to 6.0.0.4013 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
An insecure deserialization operation in the Trend Micro Endpoint Encryption PolicyServer could lead to a pre-authentication remote code execution on affected installations. Note that this vulnerability is similar to CVE-2025-49213 but is in a different method.

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

This is an insecure deserialization vulnerability in Trend Micro Endpoint Encryption PolicyServer that allows remote code execution without authentication. The flaw is similar to CVE-2025-49213 but exists in a different method within the policy server component. The critical CVSS score of 9.8 reflects the severe impact of unauthenticated RCE in a foundational security product.

MitigationApply vendor patches when available; in the interim, restrict network access to the PolicyServer to trusted management stations only and monitor for indicators of compromise.

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
Trend Micro Endpoint EncryptionApplication
Affected:< 6.0.0.4013

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

CVSS:3.1/AV:N/AC:L/PR:N/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 the installed PolicyServer version
    Locate the Trend Micro Endpoint Encryption PolicyServer component and retrieve its version information (check the product About, installation directory, or version registry key)
    Affected if The version is lower than 6.0.0.4013
  2. Confirm PolicyServer is the deployed component
    Verify that the PolicyServer component (not just the client encryption agent) is installed in the environment
    Affected if PolicyServer is installed as part of the Endpoint Encryption deployment
  3. Determine network accessibility of PolicyServer
    Identify which network ports the PolicyServer service is listening on and whether it is accessible from network segments outside trusted management stations
    Affected if PolicyServer ports are reachable from untrusted networks or non-management workstations
  4. Review PolicyServer configuration
    Examine the PolicyServer configuration files or administrative settings to confirm the vulnerable method/endpoint is enabled (the insecure deserialization flaw exists in a specific policy server method)
    Affected if The vulnerable method is exposed and operational

The environment is affected if PolicyServer version is below 6.0.0.4013 and the vulnerable method is accessible on the network.

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 6.0.0.4013 or later
Fixed in 6.0.0.4013
Interim mitigation

Apply vendor patches when available; in the interim, restrict network access to the PolicyServer to trusted management stations only and monitor for indicators of compromise.

Recommended fix Moderate confidence

Trend Micro Endpoint Encryption version 6.0.0.4013 or later

  1. 1. Verify current Trend Micro Endpoint Encryption PolicyServer version via the management console or system information
  2. 2. Download the latest version of Trend Micro Endpoint Encryption (6.0.0.4013 or later) from the Trend Micro Customer Licensing Portal or official support site
  3. 3. Review all upgrade prerequisites and system requirements in the Trend Micro documentation
  4. 4. Create a complete backup of the PolicyServer database and configuration settings
  5. 5. Schedule a maintenance window as the upgrade may require service interruption
  6. 6. Execute the upgrade installer with appropriate administrative privileges
  7. 7. Verify the PolicyServer service restarts successfully
  8. 8. Confirm the new version (6.0.0.4013 or later) is installed via management console or command line
Caveat Review release notes for potential breaking changes; major version upgrades may require migration procedures or compatibility checks with existing endpoints

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

Fix this in Trend Micro Endpoint Encryption Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,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 $8,256.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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