dbcve.org
CWE-250Weakness · CWE-250

CVE-2026-4606

CRITICAL · 10.0 CVSS v4.0 Published 2026-03-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
GV Edge Recording Manager (ERM) v2.3.1 improperly runs application components with SYSTEM-level privileges, allowing any local user to gain full control of the operating system.  During installation, ERM creates a Windows service that runs under the LocalSystem account.  When the ERM application is launched, related processes are spawned under SYSTEM privileges rather than the security context of the logged-in user.  Functions such as 'Import Data' open a Windows file dialog operating with SYSTEM permissions, enabling modification or deletion of protected system files and directories.  Any ERM function invoking Windows file open/save dialogs exposes the same risk.  This vulnerability allows local privilege escalation and may result in full system compromise.

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

GV Edge Recording Manager v2.3.1 creates a Windows service that runs under the LocalSystem account, causing all application processes and Windows file dialogs (including Import Data functions) to operate with SYSTEM-level privileges. This allows any local user to manipulate these elevated file dialogs to modify or delete protected system files, achieving full system compromise through local privilege escalation.

MitigationRestrict the ERM Windows service to run under a dedicated low-privilege service account rather than LocalSystem; apply vendor patches when available; if a patch is unavailable, implement compensating controls such as restricting physical and remote access to the 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
Network
Complexity
Low
Privileges
None
Authentication
None
User interaction
None
Scope
N

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:N/AU:N/R:I/V:C/RE:M/U:Green

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. Identify GV Edge Recording Manager installation and version
    Open Windows Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product' in PowerShell, to find GV Edge Recording Manager and confirm the installed version is 2.3.1
    Affected if The software is installed and the version is 2.3.1 (or falls within any other affected version range if later releases are identified)
  2. Locate the ERM Windows service
    Open Services console (services.msc) or run 'Get-Service | Where-Object {$_.DisplayName -like "*Recording*" -or $_.DisplayName -like "*ERM*"}' in PowerShell to find the GV Edge Recording Manager service
    Affected if A GV Edge Recording Manager service exists in the system services list
  3. Check the service logon account
    In Services console, right-click the ERM service > Properties > Log On tab; or run 'Get-WmiObject Win32_Service | Where-Object {$_.Name -like "*ERM*"} | Select-Object Name, StartName' in PowerShell
    Affected if The service Log On account is set to Local System or shows "NT AUTHORITY\SYSTEM" (this is the vulnerable configuration)
  4. Verify if the ERM service is running
    In Services console, check the service Status column; or run 'Get-Service -Name "<ERM_Service_Name>" | Select-Object Status' in PowerShell
    Affected if The service status is Running (the vulnerability is actively exploitable only when the service is running)

A system is affected if GV Edge Recording Manager v2.3.1 is installed with its service running under the LocalSystem account, allowing local users to elevate privileges via elevated file dialogs.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict the ERM Windows service to run under a dedicated low-privilege service account rather than LocalSystem; apply vendor patches when available; if a patch is unavailable, implement compensating controls such as restricting physical and remote access to the system.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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