CVE-2023-41179 Trend Micro Apex One and Worry-Free Business Security Remote Code Execution Vulnerability
Trend Micro Apex One and Worry-Free Business Security contain an unspecified vulnerability in the third-party anti-virus uninstaller that could allow an attacker to manipulate the module to conduct remote code execution. An attacker must first obtain administrative console access on the target system in order to exploit this vulnerability.
From the CISA KEV catalogue version 2026.11.06, with Cybergen analysis. Updated 6 Nov 2026.
Should You Worry?
- CISA confirmed exploitation in the wild and added it to the Known Exploited Vulnerabilities catalogue on 21 Sep 2023.
- Rated High severity (CVSS 7.2, scored by CISA).
- It has been in the catalogue for 1,142 days. Systems still unpatched now have almost certainly been scanned for it.
What It Is
A vulnerability in the 3rd party AV uninstaller module contained in Trend Micro Apex One (on-prem and SaaS), Worry-Free Business Security and Worry-Free Business Security Services could allow an attacker to manipulate the module to execute arbitrary commands on an affected installation. Note that an attacker must first obtain administrative console access on the target system in order to exploit this vulnerability.
Affected Versions
| Product | Versions |
|---|---|
| Trend Micro, Inc. Trend Micro Apex One | 2019 (14.0) to before 14.0.0.12380 |
| Trend Micro, Inc. Trend Micro Apex One | SaaS to before 14.0.12637 |
| Trend Micro, Inc. Trend Micro Worry-Free Business Security | 10.0 SP1 to before 10.0 SP1 Build 2495 |
| Trend Micro, Inc. Trend Micro Worry-Free Business Security Services | SaaS to before 6.7.3578 / 14.3.1105 |
From the public CVE record, as supplied by the vendor. Always confirm against the vendor advisory.
What To Do Now
- 1
Find it
Search your asset inventory and external attack surface for Trend Micro Apex One and Worry-Free Business Security. Include cloud images, appliances and anything a supplier runs for you.
Attack Surface Management - 2
Fix it
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Vulnerability Management - 3
Hunt for compromise
If an affected system was reachable before you patched, assume it may have been hit. Check logs, new accounts, web shells and outbound connections from the date of exposure.
Incident Response - 4
Prove it is fixed
Rescan or test the system after patching. Upgrades that fail silently and forgotten secondary instances are common.
Penetration Testing
The Compliance Clock
General guidance, not legal advice. Your obligations depend on your sector, scope and jurisdiction.
Not Sure If You Are Exposed?
Our attack surface and vulnerability teams can check your internet-facing estate for CVE-2023-41179 and every other exploited flaw on the list.