Vulnerability report

Exploited in the wild Confirmed confidence In CISA KEV

CVE-2022-40139

Trend Micro Apex One Remote Code Execution

Trend Micro Apex One · 2019 (on-prem) and SaaS

Severity
CVSS 7.2 · High
Confidence
Confirmed
Exploit status
Exploited in the wild
EPSS
3.3%
First observed
—
Last observed
—

Decision summary

What security teams need to know first

Direct answers before the deeper technical record.

What it is

CVE-2022-40139 is a vulnerability affecting Trend Micro Apex One. Improper validation of some components used by the rollback mechanism in Trend Micro Apex One and Trend Micro Apex One as a Service clients could allow...

Is it exploited?

Yes. Previdian tracks this CVE as a known exploited vulnerability. Confidence is confirmed. Listed in CISA KEV.

Who is affected?

Trend Micro Apex One 2019 (on-prem) and saas.

What should we do?

Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.

Overview

Trend Micro Apex One Remote Code Execution

Improper validation of some components used by the rollback mechanism in Trend Micro Apex One and Trend Micro Apex One as a Service clients could allow a Apex One server administrator to instruct affected clients to download an unverified rollback package, which could lead to remote code execution.

Please note: an attacker must first obtain Apex One server administration console access in order to exploit this vulnerability.

Trend Micro Affected
Trend Micro Apex One
2019 (on-prem) and SaaS
Published
19 Sep 2022
Exploitation Reported
15 Sep 2022
Attack vector
Remote
Complexity
Low
Privileges
High
User interaction
None

Tags

cisa nessus_scanner

CVE References

Exploitation evidence

Why Previdian marks this CVE as exploited

Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.

Exploited in the wild

CISA

Recorded 15 Sep 2022

A trusted third party reported exploitation.

Known exploited vulnerability sources

Per-source evidence links for KEV attestations are available through the Previdian Pro API.

Learn about Pro API access
Source Added
CISA First 2022-09-15 00:00 UTC

Detection

Operational artifacts and observed signals

Make the evidence actionable in scanner, SOC, and edge-control workflows.

Observed signals

Request targets
User-Agents
Callback hosts
0
0
0

Request targets and User-Agents available in Pro. Callback host details available in Enterprise.

Virtual patch status

No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.

Learn about virtual patches →

Scanner Artifacts

Scanner and exploit-framework references linked to this CVE.

Scanner Reference Detected
Nessus https://www.tenable.com/plugins/nessus/164982 02 Jun 2025

Risk and context

Severity, weaknesses, and research context

CVSS v3.1

7.2 High

Potential damage if exploited. Separate from whether attackers are using it.

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

EPSS

3.3%

Estimated chance of exploitation in the next 30 days. Previdian's warning comes from evidence, not this score.

Timeline

From disclosure to observed exploitation

  1. 09:27 UTC

    Nessus plugin available

    Scanner coverage available

  2. 18:01 UTC

    CVE published

    Vulnerability disclosed publicly

  3. 00:00 UTC

    Added to CISA KEV

    Listed in the CISA Known Exploited Vulnerabilities catalog

  4. 00:00 UTC

    CVE ID reserved

    Identifier reserved by the CNA

Pro API

Automate this intelligence

Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.

  • Evidence confidence and provenance
  • First-party sensor telemetry
  • PoC and scanner references
  • Affected versions and enrichment
  • Automation-ready JSON delivery

GET /api/v2/pro/kevs/CVE-2022-40139

Sample API response
{
  "cve_id": "CVE-2022-40139",
  "confidence": "Confirmed",
  "cvss_score": 7.2,
  "cvss_estimated": false,
  "epss_score": 0.03291,
  "exploit_status": {
    "exploited_in_the_wild": true,
    "active_exploitation_observed": false
  },
  "sensor_telemetry": { "attempts": 0, "sensors": 0 }
}