[KEV] Vulnerability in Trend Micro Apex One (CVE-2026-34926)
Summary
Vulnerability in Trend Micro Apex One (CVE-2026-34926). Confidential information can be exposed externally. Listed in CISA KEV — actively exploited.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory CISA KEV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-34926 has been found in Trend Micro Apex One.
Confidential information can be exposed externally. CVSS score: 6.7/10.
Note: CISA has officially confirmed this is actively exploited in the wild. Treat it with elevated urgency.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Trend Micro Apex One CVE-2026-34926" on the vendor's site.
CVE-2026-34926 (Trend Micro Apex One) — CWE-23 / CVSS v3 6.7
Attack vector: local / no user interaction
Listed in CISA KEV — actively exploited, treat as top priority.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-23) exists in Trend Micro Apex One.
Check the vendor advisory for the affected versions of Trend Micro Apex One.
Severity: Medium (CVSS 6.7/10). Confidential information can be exposed externally. Listed in CISA KEV — actively exploited in the wild, treat as top priority.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Trend Micro Apex One を使っているサービスとバージョンを洗い出す。
-
2Consider incident declaration escalate
Notify SOC / on-callCISA KEV登録済 = 実環境で悪用が観測されている。侵入の兆候があればインシデント対応宣言、無くてもパッチ適用までWAF強化を最優先で。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory security@trendmicro.com
- advisory security@trendmicro.com
- advisory NVD
- advisory cisa.gov
- JVN JVNDB-2026-016802
- patch security@trendmicro.com
- patch security@trendmicro.com
- web jvn.jp
- web github.com