dbcve.org
Apex OneApplication · Trendmicro

CVE-2026-34930

HIGH · 7.8 CVSS v3.1 Published 2026-05-21
Fix available
A fix is available. Upgrade to 14.0.0.17079 / 14.0.20731 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An origin validation vulnerability in the Apex One/SEP agent could allow a local attacker to escalate privileges on affected installations. This is similar to CVE-2026-34927 but exists in a different process protection mechanism. Please note: an attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a local privilege escalation vulnerability in Apex One (Sophos) and SEP (Symantec Endpoint Protection) agents. The flaw is an origin validation error in a process protection mechanism that allows a low-privileged attacker to bypass security controls and execute code with elevated privileges. It affects a different process protection component than the related CVE-2026-34927.

MitigationApply vendor-provided patches for Apex One and SEP agents as soon as they become available. Prioritize remediation given the high CVSS score and the requirement for initial low-privileged access, which is a common attacker foothold.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Apex OneApplication
Affected:< 14.0.0.17079< 14.0.20731

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Apex One or SEP agent installation
    Look for Trend Micro Apex One or Symantec Endpoint Protection (SEP) agent in the list of installed programs via Control Panel > Programs and Features, or check for the installation directory under C:\Program Files\Trend Micro or C:\Program Files\Symantec.
    Affected if Either product is installed, proceed to version check.
  2. Identify installed version
    Check the program version through the product's main UI (Help > About), or inspect the version information of the main executable (e.g., Apex One core service or SEP agent service) in the installation directory.
    Affected if Version cannot be determined, the detection is inconclusive.
  3. Compare version against affected ranges
    Compare your installed version number to the affected ranges: less than 14.0.0.17079 or less than 14.0.20731. Note the exact version displayed.
    Affected if Installed version falls below both 14.0.0.17079 and 14.0.20731, indicating a potentially vulnerable version.
  4. Verify process protection component status
    Check if the process protection or behavior monitoring feature is enabled in the Apex One/SEP agent security settings. This is typically found under Settings > Process Protection or Real-time Protection in the agent console.
    Affected if Process protection feature is enabled, the specific vulnerability condition is met for exploitation.

If Apex One or SEP agent is installed with a version below 14.0.0.17079 (or below 14.0.20731) AND the process protection feature is active, the environment is affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 14.0.0.17079 / 14.0.20731 or later
Fixed in 14.0.0.1707914.0.20731
Interim mitigation

Apply vendor-provided patches for Apex One and SEP agents as soon as they become available. Prioritize remediation given the high CVSS score and the requirement for initial low-privileged access, which is a common attacker foothold.

Recommended fix High confidence

Apex One 14.0.0.17079+ (or 14.0.20731+ depending on version branch)

  1. 1. Verify the current Apex One client version by checking About or the installed software list
  2. 2. Identify whether the installed version follows the 14.0.0.xxxx or 14.0.xxxx numbering scheme
  3. 3. For 14.0.0.xxxx branch: ensure the version is 14.0.0.17079 or later
  4. 4. For 14.0.xxxx branch: ensure the version is 14.0.20731 or later
  5. 5. Download the appropriate patch/upgrade from the Trend Micro Download Center or your licensed portal
  6. 6. Test the upgrade in a non-production environment first
  7. 7. Apply the upgrade following standard Apex One deployment procedures
  8. 8. Verify the version post-upgrade matches the fixed version requirements
Caveat Standard upgrade considerations apply - review release notes for any configuration or compatibility changes before deploying

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Apex One Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34930 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-34930 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data