dbcve.org
Genetec Update ServiceApplication · Genetec

CVE-2025-1789

HIGH · 7.8 CVSS v3.1 Published 2026-02-24
Fix available
A fix is available. Upgrade to 2.10.6 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
Local privilege escalation in Genetec Update Service. An authenticated, low-privileged, Windows user could exploit this vulnerability to gain elevated privileges on the affected system.

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

Local privilege escalation vulnerability in Genetec Update Service allows an authenticated, low-privileged Windows user to gain elevated (administrator/SYSTEM) privileges on the affected system. The vulnerability exists in the Update Service component and likely involves improper privilege handling or insecure file/service permissions that can be exploited by a local authenticated attacker.

MitigationApply the vendor-supplied patch for CVE-2025-1789 to all affected Genetec installations as soon as possible. In the interim, limit low-privileged user access to the Genetec Update Service and monitor for suspicious process execution.

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
Genetec Update ServiceApplication
Affected:< 2.10.6

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. Verify Genetec Update Service is installed
    Open Windows Services (services.msc) and look for 'Genetec Update Service' or check Program Files for Genetec installation directories. Alternatively, run: Get-Service -Name '*Genetec*' or check registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for Genetec entries.
    Affected if The service named 'Genetec Update Service' or 'Genetec Update Service (GUS)' is found on the system.
  2. Determine installed version of Genetec Update Service
    Check the version of the installed Genetec Update Service executable. Common paths include C:\Program Files\Genetec\Genetec Update Service\ or C:\Program Files (x86)\Genetec\Genetec Update Service\. Right-click the executable (often named UpdateService.exe or similar) and view Properties > Details, or use PowerShell: Get-Item 'C:\Program Files\Genetec\Genetec Update Service\*.exe' | Select-Object Name, Version.
    Affected if The version number displayed is lower than 2.10.6 (for example, 2.10.5, 2.9.x, etc.).
  3. Inspect service configuration and permissions
    Open Services (services.msc), right-click the Genetec Update Service, select Properties, and examine the 'Log on' tab. Also check service ACLs using PowerShell: Get-Acl 'HKLM\SYSTEM\CurrentControlSet\Services\GenetecUpdateService' | Format-List. Use icacls.exe on the service executable directory to review file permissions.
    Affected if The service runs under a privileged account (like LocalSystem or Administrator) AND low-privileged users have write/modify access to the service executable, its configuration files, or the directory where the service resides.
  4. Verify service is currently running
    In Services console, check if Genetec Update Service shows a 'Running' status. Alternatively, run: Get-Service -Name '*Genetec*' | Select-Object Status, Name.
    Affected if The service is installed AND running (or set to start automatically) on the system.

A system is affected if Genetec Update Service is installed with a version lower than 2.10.6 and runs with elevated privileges while allowing low-privileged users to modify service files or configurations.

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 2.10.6 or later
Fixed in 2.10.6
Interim mitigation

Apply the vendor-supplied patch for CVE-2025-1789 to all affected Genetec installations as soon as possible. In the interim, limit low-privileged user access to the Genetec Update Service and monitor for suspicious process execution.

Recommended fix Moderate confidence

Genetec Update Service 2.10.6

  1. Identify the current version of Genetec Update Service installed on the system
  2. Download Genetec Update Service version 2.10.6 or later from the official Genetec downloads portal or through your authorized Genetec representative
  3. Stop any services or processes related to Genetec Update Service before upgrading
  4. Run the installer for the new version with appropriate administrative privileges
  5. Follow the installation wizard prompts to complete the upgrade
  6. Restart the Genetec Update Service and verify the service is running correctly
  7. Confirm the installed version is 2.10.6 or later using the service's version information

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

Fix this in Genetec Update Service Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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 locally
dbcve dependency scanner

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