An encoding issue in the file ADSyncOUList.config may prevent the system from synchronizing with Active Directory, resulting in display issues on the User/Endpoint Directory screen in the web console.

A potential Remote Code Execution vulnerability is found in the Dashboard component.

A potential Path Traversal vulnerability is found in the Policy component.

An issue related to Activation Code expiration may cause Apex One (Mac) services to stop.

After changing the Protocol setting from UDP to SSL/TLS on the Syslog Settings screen in the web console, the Test Connection button may become inactive.

The following potential vulnerabilities are found in Apex Central:

• SQL Injection
• Cross-site scripting
• Improper access control
• EOL/Obsolete software used
• Improper cookie configuration
• CSRF (Cross-Site Request Forgery)

An issue related to Active Directory user groups may prevent the system from running the Application Control agent service.

An issue related to the Scan Cloud File feature in the Virus Scan Engine (VSAPI) may cause Trend Micro Apex One Security Agent endpoints to become unresponsive.

An issue related to IP address format processing may prevent the FTP Channel Monitoring feature in Data Loss Prevention from functioning properly on Trend Micro Apex One Security Agent endpoints.

Users may not be able to search for "Outdated Agents" using the Endpoint Status widget in the Trend Micro Apex One web console.

The system may include the Intrusion Detection System (IDS) status information in the Security Agent endpoint status export file from the Agent Management screen in the web console.

An unloading issue in the Real-time Scan service ("Ntrtscan.exe") may cause the service to stop unexpectedly and affect system performance on Security Agent endpoints.

Trend Micro Apex One Security Agent may not provide the correct virus and threat protection status in Windows Security Center.

After updating the Trend Micro Apex One Security Agent program, the system unexpectedly starts the Trend Micro Security Agent Monitor ("PccNTMon.exe") process.

Enabling the Trend Micro Unauthorized Change Prevention Service may cause a blue screen of death (BSOD) error on Trend Micro Apex One Security Agent endpoints.

An issue related to the notify change agent GUID in Trend Micro Apex One may prevent the Trend Micro Apex One Security Agent program to perform agent GUID synchronization with Endpoint Basecamp.

An issue related to the Trend Micro User Mode Hooking (UMH) component in Trend Micro Apex One Security Agent may cause the system to close Microsoft PowerPoint files after coming out of hibernation.

This Hotfix adds a new Log Transmission monitoring mechanism in Apex One as a Service.

This Hotfix updates the related modules to resolve display issues on endpoints running Windows Server 2025.

This Hotfix updates the Data Loss Prevention (DLP) module to enhance the credit card validation mechanism.

This Hotfix allows you the configure the password complexity settings for accessing the Apex Central web console.

This Hotfix enables the Trend Micro Apex One Security Agent program to support endpoints running Microsoft Windows Server 2025.

This Hotfix updates the encryption algorithm in the Trend Micro Apex One server and Security Agent programs to enhance product security.

This Hotfix updates the Damage Cleanup Engine (DCE) to version 7.5.1209 to resolve a potential Link Following Local Privilege Escalation security issue.

This Hotfix updates the Trend Micro Apex One Security Agent program to protect against potential Uncontrolled Search Path Local Privilege Escalation vulnerabilities.

This Hotfix updates the Trend Micro iCRC Common Module to version 2.83.1077 and the OpenSSL library in the module to version 3.1.7 to enhance product security.

This Hotfix updates the iCore module in Trend Micro Apex One (Mac) Security Agent to enhance detection actions for Spyware.

This Hotfix updates the Advanced Threat Scan Engine (ATSE) in Trend Micro Apex One (Mac) Security Agent to enhance product integration.

Security Agent consoles running build 13.95 display an incorrect policy name. To resolve this issue, upgrade the Security Agent to 14.0. After the Security Agent contacts the server, the policy name displays correctly.

Off-premises and Security Agents in Independent mode cannot update the Certified Safe Software Pattern from external update sources.

Coexist mode Security Agents on endpoints with Windows Defender may experience installation issues or be unable to upload data to the Apex One server due to a file locking issue. To resolve this issue, add Endpoint Sensor (ESEServiceShell.exe and ESClient.exe) in the exclusions list of Windows Defender to prevent the locking issue.

After copying a file to a remote server using a relative path as the source, Apex One is unable to translate the relative path into the full system directory.

The quality of RCA analysis chain image files is reduced when viewing the files using Windows 10 Photo Viewer.

When attempting to start a Historical Investigation from the Attack Discovery Detections widget that includes Registry value name or Registry value data criteria, the Historical Investigation displays an error message if the length of the Registry value name exceeds 260 characters or the Registry value data exceeds 64 characters.

After updating the Attack Discovery Pattern file (tmesadp.ptn) on Security Agents, a database schema error may occur that causes the Endpoint Sensor feature to continuously report the same detections to the server during each synchronization. This causes duplicate records to display on the Apex Central server.

Root Cause Analysis email attachment results may also include temporary files created when the user saved the file.

The number of matched endpoints that display on a Root Cause Analysis chain may appear to be greater than the total if the Security Agent on an endpoint was uninstalled or no longer reports to the same managing server.

The Endpoint Sensor service may have high memory usage.

The Endpoint Sensor may have high peak CPU usage occasionally.

Endpoint Sensor has CPU peak during Windows Update phase.

The user or account name in ADE detection may be empty.

The EC module may stop responding while handling NULL data which may cause the ESEService and ADE functionality to behave abnormally.

In rare conditions, ESEService stops responding while unloading.

A time zone issue may cause the system to display different log generation time information in the web console. In the web console, the system displays the log generation time in the time zone of the Apex One server.

• The Apex One server stores the log generation time information in GMT+0.
• The Security Agent sends the log generation time information (GMT+0 or local time) to the Apex One server.

After enabling the Scan Time Machine option for Manual Scan and Scheduled Scan, Apex One (Mac) cannot perform any actions (clean, quarantine, or delete) on detected malware threats due to a permission limitation in Mac OS. Configured scan actions are displayed as unsuccessful in the product logs.

When performing a historical investigation on Apex One (Mac) endpoints, the system replaces a slash (/) with a colon (:) in file names, preventing users from searching for file names that contain backslashes in investigation results.

To resolve this issue, use a colon (:) to search for the files.