CVE-2026-34926
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 · uneditedA 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.
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 confidenceA directory traversal vulnerability in Apex One on-premise server allows a pre-authenticated attacker with administrative credentials to modify a key table on the server and inject malicious code that can be pushed to connected agents.
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
- High
- Privileges
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:L
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 versionAccess the Apex One server console, navigate to Administration > About, or check the Windows Programs and Features list for the installed version numberAffected if The installed version is below 14.0.0.17079 or below 14.0.20731 (check both version strings as the numbering scheme varies)
-
Verify admin authentication is requiredConfirm that the Apex One management console requires valid administrative credentials for access. Check if anonymous or guest access is enabled in the security settingsAffected if Administrative credentials are required, but the server is internet-facing or accessible to untrusted users who may have obtained valid admin credentials
-
Inspect web server access logs for path traversal patternsReview Apex One web server logs (typically in the installation path under \logs\ or \web\logs\) for suspicious requests containing sequences like ../, ..\, or encoded path traversal charactersAffected if Logs contain path traversal attempts targeting database table modification endpoints, particularly POST requests to table modification utilities
-
Check for unauthorized database table modificationsQuery the Apex One database (typically SQL Server or embedded) for unexpected entries in key tables, particularly any modified stored procedures or unexpected executable content in data fieldsAffected if Database tables contain suspicious entries, modified stored procedures, or code that was not intentionally deployed by administrators
-
Review agent update sourcesExamine the Apex One agent configuration to verify that update sources point only to the legitimate internal server, and check for any unauthorized update package distributionsAffected if Agents are receiving updates from unexpected sources or if there are unauthorized update packages on the server
-
Audit administrative user accountsReview the list of administrative users in Apex One (Administration > Account Management > User Accounts) for any unauthorized or unexpected admin accountsAffected if New or unexpected administrative accounts exist that were not created by known administrators
A user is affected if their Apex One version falls within the affected ranges AND the server is accessible to attackers who could obtain or already possess administrative credentials to exploit the path traversal for database injection.
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 when available; restrict administrative access to the Apex One server and implement least-privilege principles; monitor for unauthorized table modifications.
Apex One version 14.0.0.17079 or later (or version 14.20731 or later)
- Obtain the latest Apex One server version from the official Trend Micro download portal or your licensed channel
- Ensure you have a complete backup of the Apex One server database and configuration
- Download the patch or upgrade package for version 14.0.0.17079 (or 14.20731 and later)
- Stop the Apex One services on the server before applying the update
- Apply the upgrade following the official Trend Micro upgrade documentation
- Verify the upgrade was successful by checking the server version in the Apex One console
- Restart the Apex One services
- Confirm that the directory traversal vulnerability is no longer present by reviewing release notes or running security validation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34926 — 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-34926 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