dbcve.org
Race ConditionWeakness · CWE-362

CVE-2026-35099

HIGH · 7.4 CVSS v3.1 Published 2026-04-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
79/100
Remediation priority · High
No privileges 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
Lakeside SysTrack Agent 11 before 11.5.0.15 has a race condition with resultant local privilege escalation to SYSTEM. The fixed versions are 11.2.1.28, 11.3.0.38, 11.4.0.24, and 11.5.0.15.

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 · high confidence

Lakeside SysTrack Agent before version 11.5.0.15 contains a race condition vulnerability that can be exploited to achieve local privilege escalation to SYSTEM level. The vulnerability requires local access but enables an authenticated attacker to escalate privileges beyond their assigned permissions. Fixed versions are available across all supported branches.

MitigationUpdate the SysTrack Agent to one of the fixed versions (11.2.1.28, 11.3.0.38, 11.4.0.24, or 11.5.0.15) depending on the current branch in use. Prioritize higher CVSS environments given the privilege escalation to SYSTEM.

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

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:N/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. Verify SysTrack Agent is installed
    Check for SysTrack Agent installation on the system using standard software inventory tools, Program Files directory, or registry keys related to Lakeside products
    Affected if SysTrack Agent is present on the system
  2. Identify installed SysTrack version
    Use system inventory tools, check the installed software list, or query the SysTrack Agent directly for its version number
    Affected if The version returned is earlier than 11.5.0.15, or falls in the ranges 11.2.x before 11.2.1.28, 11.3.x before 11.3.0.38, or 11.4.x before 11.4.0.24
  3. Confirm the agent service is running
    Verify that the SysTrack Agent service or process is active on the system, as the race condition requires the vulnerable code path to be executing
    Affected if The agent service is running on an affected version
  4. Check for available version branches
    Determine which version branch (11.2, 11.3, 11.4, or 11.5) is installed by examining the full version string
    Affected if The installed branch version is below its respective fix (11.2.1.28, 11.3.0.38, 11.4.0.24, or 11.5.0.15)

The environment is affected if SysTrack Agent is installed with a version prior to 11.5.0.15 (or below the relevant branch fix) and the agent service is actively running, enabling a local authenticated attacker to exploit the race condition for SYSTEM privilege escalation.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the SysTrack Agent to one of the fixed versions (11.2.1.28, 11.3.0.38, 11.4.0.24, or 11.5.0.15) depending on the current branch in use. Prioritize higher CVSS environments given the privilege escalation to SYSTEM.

Recommended fix High confidence

Lakeside SysTrack Agent 11.5.0.15 (or latest version in your current branch: 11.2.1.28, 11.3.0.38, or 11.4.0.24)

  1. 1. Identify the current version of Lakeside SysTrack Agent 11 installed on the system
  2. 2. If the current version is before 11.2.1.28, plan upgrade to version 11.5.0.15
  3. 3. If the current version is between 11.2.1.28 and 11.3.0.37, upgrade to version 11.3.0.38
  4. 4. If the current version is between 11.3.0.38 and 11.4.0.23, upgrade to version 11.4.0.24
  5. 5. If the current version is between 11.4.0.24 and 11.5.0.14, upgrade to version 11.5.0.15
  6. 6. Obtain the upgrade package from the official Lakeside Software vendor channels
  7. 7. Apply the upgrade following standard deployment procedures
  8. 8. Verify the installation was successful and the version is now at or above the fixed version for your branch
Caveat Within same major version (11.x), breaking changes unlikely; however, test in non-production environment before broad deployment

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-35099 — 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-35099 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