An internal issue may prevent the system from synchronizing account information from Trend Vision One.

An issue related to the ActiveUpdate module may cause the system to continuously download update components.

After a syslog connection test, the system may not terminate the TLS connection properly.

A potential Server-Side Request Forgery Vulnerability is found in the Threat Intelligence component.

A potential Server-Side Request Forgery Vulnerability is found in the Update module.

A potential Improper Authentication Privilege Escalation Vulnerability is found in the Single-Sign On module.

Potential vulnerabilities are found in the PHP library used in Trend Micro Apex Central.

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.

An issue related to the time format may prevent Trend Micro Apex Central from obtaining status updates from ScanMail for Microsoft Exchange.

An unsuccessful Open Database Connectivity (ODBC) connection may prevent Trend Micro Apex Central from generating reports.

The system may not send endpoint information to Trend Vision One.

An issue may prevent scan action configuration for Virtual Analyzer Suspicious Objects in the web console.

When opening files with exclusive access (non-shared mode), PowerShell scripts may not execute successfully on Trend Micro Apex One Security Agent endpoints.

When Trend Micro Apex One Security extracts 7z file attachments and stores the extracted files in a temp folder, third-party security programs may scan the temp folder resulting in high CPU usage on Security Agent endpoints.

The system may not install Trend Micro Security Agent on endpoints successfully using the installation package (EXE).

Trend Micro Apex One Security Agent is unable to detect Hong Kong identity card data containing lower-case alphabets.

When uploading files containing sensitive information from Security Agent endpoints to cloud storage, the system may not apply the exclusion settings.

After updating Trend Micro Apex One Security Agent to Build 14.0.14492, the web console displays the offline status for multiple server endpoints.

A program memory leak issue in the TMCCSF.exe service may affect system performance.

When Trend Micro Firewall is enabled, the system is unable to access the ZScaler application.

Trend Micro Apex One may not detect suspicious files in a hidden folder with an empty folder name on USB storage devices.

File Reputation Service may become unavailable on Security Agent endpoints.

An issue related to Data Loss Prevention (DLP) may prevent users from saving or deleting files on USB devices that are granted read access in Device Control.

After moving a Security Agent to another Trend Micro Apex One server, the Security Agent update process may run continuously.

This Hotfix updates PCRE regular expressions to enhance compatibility with PCRE2.

This Hotfix enables Trend Micro Apex Central to reset the suspicious object cache index if the number of entries exceeds the specified threshold.

This Hotfix enhances the migration process for XDRLogAgent settings.

This Hotfix enables Trend Micro Apex Central to display notifications for all account types in the web console.

This Hotfix updates the Open Database Connectivity (ODBC) driver to 17.10.6.

This Hotfix enhances the Data Loss Prevention syslog to display the server FQDN instead of the Product Tree name for the dvhost.

This Hotfix adds the "Dynamic Intelligence Mode" setting to automatically adjust monitoring levels to optimize security responses based on analyzing detected threats, user behavior, and system context.

This Hotfix updates the Virus Scan Engine (VSAPI) to version 25.530.1011 and the Advanced Threat Scan Engine (ATSE) to version 25.530.1011 to protect against a Link Following Local Privilege Escalation security issue.

This Hotfix updates the PHP component in Trend Micro Apex One to enhance product security.

This Hotfix updates the Trend Micro Apex One Security Agent program to protect against a potential Local Privilege Escalation Vector security issue.

This Hotfix updates the related modules in Trend Micro Apex One to protect against the Virus Scan Engine Link Following Local Privilege Escalation Vulnerability. (ZDI-CAN-24972)(CVSS 3.0, Score 7.8)

This Hotfix updates the Behavior Monitoring Core Service module to version 2.98.2105 and Behavior Monitoring Core Drive module to version 2.98.2111 to enhance the Security Agent self-protection capabilities.

This Hotfix updates the iCore module in Trend Micro Apex One (Mac) Security Agent to enhance product performance.

This Hotfix updates the Trend Micro Apex One (Mac) Security Agent to enhance the integration with Trend Micro Service Gateway.

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.