CVE Tools

CVE-2026-34926

Exploited in the wild. In CISA KEV since 2026‑05‑21. Fixed versions are out.

Published Updated Sources: CVE.org, NVD, BDU

What to do

Find your product and version, then upgrade to the build on the right.

  • Trend Micro, Inc. TrendAI Apex OneAffected: ≥ 2019 (14.0), < 14.0.0.17079Upgrade to: 14.0.0.17079Stated by: CVE record
  • Trend Micro, Inc. TrendAI Apex One as a ServiceAffected: ≥ SaaS, < 14.0.20731Upgrade to: 14.0.20731Stated by: CVE record
  • Trendmicro Apex OneAffected: < 14.0.0.17079Upgrade to: 14.0.0.17079Stated by: NVD
  • Trend Micro Apex One as a ServiceAffected: до 14.0.20731Upgrade to: not statedStated by: BDU
  • Trend Micro Apex OneAffected: до 14.0.0.17079Upgrade to: not statedStated by: BDU

Versions as the sources state them. Full version matrix after sign-in

Coverage timeline

0 publishers
  1. Added to CISA KEV catalog

    ·CISA KEV

Sourced from public security reporting — each date is when it was published, not when it happened. 1 further article named this CVE in wider roundups without reporting it as a distinct event.

What it is

From the CVE record

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.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS45th
CISA KEV
CISA KEV

Listed as exploited in the wild since 2026-05-21.

US federal agencies must remediate by 2026-06-04.

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

No public exploit or proof of concept found in the sources we track.

EPSS

0.5% chance of exploitation activity in the next 30 days, which ranks it in the 45th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

16 events over 132 days, from the signal feeds we watch.

  1. EPSS band changemoderate → low
  2. EPSS band changemoderate → lowepss band change
  3. Patch availablerecord updated
  4. EPSS band changelow → moderate
  5. EPSS band changelow → moderate
  6. EPSS band changelow → moderate

Affected products

Technical detail

CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:L

Scored 6.7 by NVD.

How it is reached

  • Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
  • Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
  • Privileges Required HighRequires admin or elevated privileges
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope ChangedThe exploit can affect other components (e.g. sandbox escape, host compromise from VM)

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity LowData modification is possible but limited in scope or consequence
  • Availability LowReduced performance or intermittent disruption of service

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next exploited one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Apex One, not every advisory. This one: actively exploited.