dbcve.org
Apex OneApplication · Trendmicro

CVE-2025-49155

HIGH · 8.8 CVSS v3.1 Published 2025-06-17
Fix available
A fix is available. Upgrade to 14.0.0.14002 / 14.0.14492 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 uncontrolled search path vulnerability in the Trend Micro Apex One Data Loss Prevention module could allow an attacker to inject malicious code leading to arbitrary code execution on affected installations.

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

An uncontrolled search path vulnerability exists in the Trend Micro Apex One Data Loss Prevention (DLP) module, where the application fails to properly validate the path when loading executable code or DLLs. An attacker can place malicious code in a search path location that the application uses, causing it to load and execute the attacker's code with the privileges of the affected process, leading to arbitrary code execution.

MitigationApply the vendor-provided security patch or update to the Trend Micro Apex One DLP module. Additionally, ensure that the application directories are not writable by non-privileged users and monitor for suspicious DLLs or executables in application 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
Apex OneApplication
Affected:< 14.0.14492>= 14.0.0.12994, < 14.0.0.14002

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Confirm Apex One installation
    Check if Trend Micro Apex One is installed on the system. This can be done via the Windows Add/Remove Programs list, or by looking for the installation directory (commonly C:\Program Files\Trend Micro\Apex One or similar).
    Affected if Apex One is not installed, the vulnerability does not apply.
  2. Identify installed Apex One version
    Open the Apex One console or check the product version information. Typically found in Help > About, or in the Windows installed programs list. Note the full version number including the build number.
    Affected if The exact version cannot be determined or the product is not present.
  3. Compare version to affected ranges
    Compare the installed version number to the affected ranges: version 14.0.0.12994 or higher but lower than 14.0.0.14002, OR any version lower than 14.0.14492.
    Affected if Installed version falls within 14.0.0.12994 <= version < 14.0.0.14002 OR version < 14.0.14492.
  4. Verify DLP module status
    Access the Apex One console and check whether the Data Loss Prevention (DLP) module is enabled. This is typically found under the DLP settings or policy configuration.
    Affected if The DLP module is enabled and the version is in the affected range.
  5. Inspect application directories for suspicious files
    Examine the Apex One installation directory and subdirectories for unexpected .exe or .dll files, particularly in locations where the application loads modules. Look for files with recent modification dates or names that do not match known Trend Micro components.
    Affected if Unexpected executables or DLLs are present in the application directories.

A user is affected if Apex One with the DLP module is installed and the installed version falls within 14.0.0.12994 to 14.0.14001, or is below 14.0.14492.

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 14.0.0.14002 / 14.0.14492 or later
Fixed in 14.0.0.1400214.0.14492
Interim mitigation

Apply the vendor-provided security patch or update to the Trend Micro Apex One DLP module. Additionally, ensure that the application directories are not writable by non-privileged users and monitor for suspicious DLLs or executables in application directories.

Recommended fix Moderate confidence

Apex One version 14.0.14492 or later (or the latest available version within the 14.0.x branch)

  1. 1. Identify the current installed version of Trend Micro Apex One
  2. 2. Navigate to the Trend Micro Apex One management console
  3. 3. Go to Updates > Component Updates to check for available patches
  4. 4. Apply the latest security patch or hotfix for Apex One
  5. 5. Verify the installation completed successfully and the version has been updated
  6. 6. Restart the Apex One services if required by the update
Caveat Standard precautions apply: back up configuration before updating, test in non-production environment first, and schedule during maintenance window

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

Fix this in Apex One Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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