A directory traversal vulnerability in the Apex One (on-premise) server could allow a pre-authenticated local attacker to modify a key table
Affects the on-premise Apex One 2019 (14.0) server and agent builds below 17079 on Windows, English; Apex One as a Service is not affected. Fixed in SP1 CP Build 18012 for existing SP1 users.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Actively exploited
- Fix
- Fixed in 14.0.0.17079, 14.0.20731
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The Apex One on-premise server is affected by this vulnerability, which could allow an attacker who already has local access and administrative credentials to the server to modify a key table. Successful exploitation could let the attacker insert malicious code that is then deployed to agents on affected installations.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
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.
Timeline
- Added to CISA KEV
CISA has evidence of exploitation in the wild
- CVE published
- Record last updated
- CISA remediation deadline
Due date for US federal agencies to patch
Affected versions
- Trend Micro, Inc. TrendAI Apex One
From 2019 (14.0) · fixed in 14.0.0.17079
- Trend Micro, Inc. TrendAI Apex One as a Service
From SaaS · fixed in 14.0.20731
References 4
success.trendmicro.com
jvn.jp
jpcert.or.jp
Questions about CVE-2026-34926
What does this mean?
A directory traversal flaw lets a pre-authenticated local attacker modify a key table on the Apex One server. The attacker could use that change to inject malicious code, which is then deployed to agents on affected installations.Source: success.trendmicro.com
Am I affected, and how do I check?
The on-premise Apex One 2019 (14.0) server and agent builds below 14.0.0.17079 are affected, per the reported Windows English builds. Apex One as a Service is not affected, as the advisory states that the issue is only exploitable on the on-premise version. Check the build version of the server and agents to compare against 17079.Source: success.trendmicro.com
What should I do about it?
Upgrade on-premise Apex One to SP1 CP Build 18012, which is the listed fix for existing SP1 users.Source: success.trendmicro.com
Is it being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2026-05-21, which means it has evidence of attacks. No public exploit code is tracked.Source: cisa.gov, cve.now feed data