CVE-2026-34927
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 · uneditedAn origin validation vulnerability in the Apex One/SEP agent could allow a local attacker to escalate privileges on affected installations. 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 confidenceThis is an origin validation vulnerability in Trend Micro Apex One and Symantec Endpoint Protection (SEP) agents that allows a local attacker with low-privileged code execution to escalate to higher privileges. The vulnerability stems from improper validation of the origin of requests or actions within the security agent, potentially allowing an attacker to bypass local security boundaries.
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< 14.0.0.17079< 14.0.20731CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Apex One versionCheck the installed version via the Windows Registry at HKLM\SOFTWARE\TrendMicro\Apex One\CurrentVersion or via the program's About/Help dialog in the consoleAffected if The installed version is below 14.0.0.17079 or below 14.0.20731 (note: two different build ranges indicate different release tracks)
-
Confirm Apex One service is runningOpen Services.msc and locate the 'Apex One' or 'OfficeScan' service, or run 'sc query' for the service statusAffected if The service is running and the version check above shows a vulnerable version
-
Verify low-privilege code execution is possibleCheck if non-admin users can execute code by examining local user group memberships and any application whitelisting policies, or test creating a low-privilege processAffected if Low-privileged users have the ability to run arbitrary code or scripts on the system
-
Check for recent privilege escalation indicatorsReview Windows Security event logs (Event IDs 4624, 4625, 4672) and the Apex One activity logs for suspicious process creation or privilege assignment eventsAffected if Log entries show low-privilege processes spawning higher-privilege Apex One components unexpectedly
You are affected if Apex One is installed with a version below 14.0.0.17079 or below 14.0.20731 and the service is running on your system.
Generated from the published advisory. Verify against your own configuration.
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 · scoped14.0.0.1707914.0.20731
Apply vendor-provided patches for Apex One and SEP agents as soon as they become available, and ensure least-privilege principles are followed to limit the initial attack surface.
14.0.0.17079 or 14.0.20731 (for the 14.0.x branch)
- 1. Identify the current Apex One version by checking the product UI or using the Apex One built-in version checker
- 2. Navigate to the Trend Micro Download Center or log into the Trend Micro Customer Licensing Portal
- 3. Download the fixed Apex One version (14.0.0.17079 for the 14.0 branch or 14.0.20731 for the 14.0.207xx branch)
- 4. Review the Apex One installation and upgrade documentation from Trend Micro before proceeding
- 5. Create a backup of the current Apex One configuration and database
- 6. Test the upgrade in a non-production environment first to verify compatibility with existing systems and integrations
- 7. Apply the upgrade to the Apex One server following standard Trend Micro upgrade procedures
- 8. After upgrade completion, verify the Apex One version reflects the fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34927 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-34927 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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