CVE-2025-49154
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 · uneditedAn insecure access control vulnerability in Trend Micro Apex One and Trend Micro Worry-Free Business Security could allow a local attacker to overwrite key memory-mapped files which could then have severe consequences for the security and stability of 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 confidenceThis is a local privilege escalation vulnerability in Trend Micro endpoint security products where improper access controls allow a low-privileged attacker to overwrite memory-mapped files. This could enable the attacker to bypass security controls, escalate privileges, or cause system instability.
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= 10.0>= 6.7.0.0, < 6.7.3954>= 14.0.0, < 14.3.1299< 14.0.14492>= 14.0.0.12994, < 14.0.0.14002CVSS 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.
-
Identify installed Trend Micro productCheck the installed programs list in Control Panel or use registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for installed security products, or check for running processes like tmcc.exe, TMBMServer.exe, or Apex One servicesAffected if Any of the following products are installed: Worry Free Business Security 10.0, Worry Free Business Security Services versions 6.7.0.0-6.7.3953 or 14.0.0-14.3.1298, or Apex One versions below 14.0.14492 or between 14.0.0.12994 and 14.0.0.14001
-
Verify product versionFor Worry Free Business Security: open the console and check About or run 'tmcfgsvc.exe -v'. For Worry Free Business Security Services: check the services console or use the management portal version info. For Apex One: check the Apex One console or run 'ofcscan.ini' version tagAffected if The installed version falls within the affected ranges listed above
-
Check for the vulnerable serviceIdentify if the Trend Micro Security or Apex One services are running. Open Services.msc and look for 'Trend Micro Security Service', 'Trend Micro Worry-Free Business Security', or 'Apex One' related servicesAffected if The vulnerable Trend Micro security services are running on the system
-
Inspect directory permissionsCheck permissions on the Trend Micro installation directory (typically C:\Program Files\Trend Micro or C:\Program Files\Worry-Free Business Security). Use icacls or right-click Properties > Security to view permissionsAffected if Low-privileged or standard users have write permissions to the security product directories or subfolders containing executable or configuration files
The system is affected if a Trend Micro endpoint security product from the affected version ranges is installed AND low-privileged users can modify files in the product installation directories.
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 · scoped6.7.395414.0.0.1400214.0.14492
Apply vendor patches when available; until then, restrict low-privileged user access to security product directories and monitor for suspicious file modifications.
Upgrade to the latest version of the respective product (Apex One or Worry-Free Business Security/Services) - minimum fixed versions: Apex One 14.0.14492 or 14.0.0.14002; Worry-Free Business Security Services 6.7.3954 or 14.3.1299
- 1. Identify the currently installed version of Trend Micro Apex One or Worry-Free Business Security on the target system
- 2. For Worry-Free Business Security Services: upgrade to version 6.7.3954 or later, or upgrade to version 14.3.1299 or later
- 3. For Worry-Free Business Security version 10.0: contact Trend Micro support for specific patch guidance or upgrade to the latest available version
- 4. For Apex One: upgrade to version 14.0.14492 or later, or upgrade to version 14.0.0.14002 or later
- 5. Verify the upgrade was successful by checking the product version in the console
- 6. Test that critical security features (real-time scanning, update functionality) are operating normally
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49154 — 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-49154 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