CVE REMEDIATION GUIDE
CISA KEV · Known exploitedMediumFixed-version data available

CVE-2026-34926 remediation guide

Trend Micro, Inc. TrendAI Apex One, TrendAI Apex One as a Service, apex one

A directory traversal vulnerability in the Apex One (on-premise) server could allow a pre-authenticated local attacker to modify a key table on the server to inject malicious code to deploy to agents on affected installations. This vulnerability is only exploitable on the on-premise version of Apex One and a potential attacker must have access to the Apex One Server and already obtained administrative credentials to the server via some other method to exploit this vulnerability.

Open CVE record
ProductTrend Micro, Inc. TrendAI Apex One, TrendAI Apex One as a Service, apex one
Affected versions>= 2019 (14.0) < 14.0.0.17079, >= SaaS < 14.0.20731, < 14.0.0.17079, < 14.0.20731
Fixed versions14.0.0.17079, 14.0.20731
Priority basisImmediate · CVSS 6.7 · EPSS 12.7%
01

Identify the affected asset

Confirm whether Trend Micro, Inc. TrendAI Apex One, TrendAI Apex One as a Service, apex one is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= 2019 (14.0) < 14.0.0.17079, >= SaaS < 14.0.20731, < 14.0.0.17079, < 14.0.20731. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

CISA has listed this vulnerability in the Known Exploited Vulnerabilities catalog. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.