basicsecurity.net
Proof, not just disclosure.
Threats / Trend Micro / CVE-2022-40139
CVE-2022-40139 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Trend Micro Apex One and as a Service vulnerability

Trend Micro Apex One and Apex One as a Service contain improper validation of rollback mechanism components, enabling remote code execution.

Verdict

Today item — known-exploited.

An attacker can exploit insufficient validation in the rollback mechanism to achieve remote code execution on affected Apex One endpoints. This vulnerability has been observed in active exploitation.

CISA KEV Yes · 2022-09-153EPSS 0.02934 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
4 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-09-15).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.02934 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Trend Micro, Apex One and Apex One as a Service. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-353 CWE-353, CWE-641 CWE-641.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I identify that the rollback validation mechanism in Apex One lacks proper integrity checks.
Business
Security endpoint protection is compromised at the mechanism level, creating a direct path to system compromise.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I craft a malicious rollback component that bypasses validation controls.
Business
Endpoint detection and response capabilities are undermined before they can function.
3

Lateral reach — past segmentation narrative 3

Attacker
I deliver the malicious component to trigger remote code execution on the target system.
Business
Attackers gain arbitrary code execution on protected endpoints, defeating the security solution entirely.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 4 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by trendmicro (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by trendmicroCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.