The Zero Day Initiative has published ZDI-26-1030, disclosing an unpatched local privilege escalation vulnerability in G DATA Total Security tracked as CVE-2026-19776 (CVSS 3.1: 7.8 High). The flaw resides in the TSNxGService component and stems from improper handling of filesystem links — a classic link following weakness that allows a low-privileged local attacker to coerce a service running with elevated privileges into performing operations on attacker-controlled targets, ultimately gaining unauthorized privilege escalation to SYSTEM-level context.
There is no vendor patch available at the time of disclosure. That makes this a true zero-day exposure window for every organization running G DATA Total Security endpoints. Because antivirus/EDR agents are ubiquitous, run with the highest privileges on the box, and are trusted implicitly by most security tooling, a privilege escalation primitive inside the AV itself is a worst-case building block for post-compromise tradecraft. Ransomware operators and initial access brokers routinely chain local privilege escalation bugs in security products with phishing- or loader-delivered initial footholds — and in 2025–2026 we have repeatedly seen AV/EDR privilege escalation flaws folded into intrusions within days of public disclosure.
Defenders running G DATA need to act now on detection and hardening, not when the patch lands.
Technical Analysis
Affected Products and Component
- Product: G DATA Total Security (consumer and managed endpoint installations)
- Component:
TSNxGService— a G DATA background service that executes with elevated (SYSTEM) privileges - Platform: Windows endpoints running affected builds of G DATA Total Security
- Identifier: CVE-2026-19776 / ZDI-26-1030
- CVSS 3.1: 7.8 (High) — vector consistent with local, low-privilege-required exploitation (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H)
How the Vulnerability Works (Defender's View)
The vulnerability class is link following (CWE-59: Improper Link Resolution Before File Access). The exploitation pattern for this class of bug in security products is well understood:
- Attacker precondition: The adversary must already be able to execute code in a low-privileged context on the target — e.g., via a phished user, a loader, or a compromised standard account. This is a post-initial-access primitive, not a remote entry point.
- Link placement: The attacker identifies a filesystem path that the privileged
TSNxGServiceprocess reads, writes, deletes, or moves during normal operation (quarantine handling, temp/working directories, log rotation, update staging are common offenders in this bug class). The attacker plants a symbolic link, NTFS junction, or hardlink at that path pointing to an attacker-chosen target — typically a protected system file, service binary path, or registry-adjacent artifact. - Privileged operation follows the link: When
TSNxGServiceperforms its routine operation as SYSTEM, it follows the attacker-planted link and acts on the target — writing attacker-controlled content into a privileged location, deleting or corrupting a protected file, or changing ACLs. - Privilege escalation: The attacker converts that primitive into code execution as SYSTEM — commonly by hijacking a service binary path, overwriting a DLL loaded by a privileged service, or abusing the write to plant a scheduled task or payload in a privileged directory.
Key exploitation characteristics defenders should internalize:
- Low complexity, no user interaction — once the attacker has local code execution, the technique is deterministic and reliable.
- Exploitation requires NTFS object manager knowledge (junctions via
mklink /J, hardlinks viamklink /H, or raw reparse point manipulation viaCreateSymbolicLink/NtSetInformationFile), but public tooling (e.g., the well-known symboliclink-testing-tools methodology) has made this trivially repeatable. - The AV's self-protection may paradoxically help the attacker — because security products exclude their own directories from third-party tampering scrutiny, malicious link placement under G DATA working paths can evade other controls.
Exploitation Status
- Patch status: Unpatched at disclosure. ZDI published the advisory under its standard coordinated disclosure process after the vendor failed to ship a fix within the disclosure window.
- Public PoC: ZDI's advisory is the primary public technical reference; treat functional exploitation as imminent. Historically, link-following bugs in endpoint security products are reproduced by researchers within days of disclosure.
- CISA KEV: Not listed at time of writing — monitor the KEV catalog; if active exploitation is confirmed, federal remediation deadlines will follow.
- Active exploitation: No confirmed in-the-wild campaigns reported yet — this is the window to get detection in place before that changes.
Detection & Response
Link-following exploitation against an AV service has strong, high-signal behavioral fingerprints: low-privileged processes creating reparse points/junctions in or near G DATA paths, and the G DATA service performing file operations outside its normal scope. The detections below are tuned to minimize noise — junction creation by standard users in security-product directories is genuinely rare in enterprise environments.
SIGMA Rules
---
title: Suspicious Link or Junction Creation by Non-System Process Targeting G DATA Paths
id: 4e2b9c71-6a3d-4f58-b21e-9c7d5a830f14
status: experimental
description: Detects low-privileged processes creating NTFS junctions, symlinks, or hardlinks via mklink or similar tooling, a precursor to link-following privilege escalation such as CVE-2026-19776 against G DATA TSNxGService.
references:
- https://www.zerodayinitiative.com/advisories/ZDI-26-1030/
- https://attack.mitre.org/techniques/T1068/
- https://cwe.mitre.org/data/definitions/59.html
author: Security Arsenal
date: 2026/04/06
tags:
- attack.privilege_escalation
- attack.t1068
logsource:
category: process_creation
product: windows
detection:
selection_tool:
Image|endswith:
- '\cmd.exe'
- '\mklink.exe'
- '\powershell.exe'
- '\pwsh.exe'
selection_cmd:
CommandLine|contains:
- 'mklink'
- '/J '
- '/H '
- '/D '
- 'New-Item -ItemType SymbolicLink'
- 'New-Item -ItemType Junction'
- 'New-Item -ItemType HardLink'
selection_path:
CommandLine|contains:
- 'G DATA'
- 'GDATA'
- 'TSNxG'
condition: selection_tool and selection_cmd and selection_path
falsepositives:
- Rare G DATA support or troubleshooting scripts; verify with the endpoint owner
level: high
---
title: Privileged G DATA TSNxGService Accessing Files Outside Expected Directories
id: 8d14a7c3-2b6e-4f91-a5d0-7e39c24b8f60
status: experimental
description: Detects the G DATA TSNxGService process performing sensitive file operations on protected system locations or unexpected paths, consistent with a successful link-following redirection (CVE-2026-19776) writing to or deleting attacker-targeted files as SYSTEM.
references:
- https://www.zerodayinitiative.com/advisories/ZDI-26-1030/
- https://attack.mitre.org/techniques/T1068/
author: Security Arsenal
date: 2026/04/06
tags:
- attack.privilege_escalation
- attack.t1068
- attack.defense_evasion
logsource:
category: file_event
product: windows
detection:
selection_service:
Image|endswith: '\TSNxGService.exe'
selection_target:
TargetFilename|contains:
- '\Windows\System32\drivers\'
- '\Windows\System32\config\'
- '\Windows\SysWOW64\'
filter_expected:
TargetFilename|contains:
- '\G DATA\'
condition: selection_service and selection_target and not filter_expected
falsepositives:
- Legitimate G DATA driver updates touching System32\drivers; correlate with vendor update windows
level: critical
---
title: Reparse Point Creation in Security Product Directories via File System Audit
id: b7f3e8a1-9c42-4d65-ae17-5f08b3d926c4
status: experimental
description: Detects reparse point (junction/symlink) attribute changes within G DATA installation or working directories by non-system accounts, an early-stage indicator of CVE-2026-19776 exploitation staging.
references:
- https://www.zerodayinitiative.com/advisories/ZDI-26-1030/
- https://cwe.mitre.org/data/definitions/59.html
author: Security Arsenal
date: 2026/04/06
tags:
- attack.privilege_escalation
- attack.t1068
logsource:
category: file_change
product: windows
detection:
selection:
TargetFilename|contains:
- '\ProgramData\G Data\'
- '\Program Files\G Data\'
- '\Program Files (x86)\G Data\'
filter_system:
Image|endswith:
- '\System'
- '\TSNxGService.exe'
- '\MsMpEng.exe'
- '\TiWorker.exe'
- '\msiexec.exe'
condition: selection and not filter_system
falsepositives:
- G DATA installer or updater activity; correlate with change tickets and update windows
level: high
KQL — Microsoft Sentinel / Defender
This query hunts the two-stage pattern: link/junction creation referencing G DATA paths by non-privileged processes, followed by TSNxGService activity touching protected system locations. Run it across a 14-day window and alert on any hits — in a clean environment these should be near zero.
let Lookback = 14d;
let LinkCreation =
DeviceProcessEvents
| where TimeGenerated > ago(Lookback)
| where ProcessCommandLine has_any ("mklink", "/J ", "/H ", "/D ", "SymbolicLink", "Junction", "HardLink")
| where ProcessCommandLine has_any ("G DATA", "GDATA", "TSNxG")
| where InitiatingProcessAccountName !in~ ("system", "local service", "network service")
| project LinkTime=TimeGenerated, DeviceName, LinkAccount=InitiatingProcessAccountName, LinkCmd=ProcessCommandLine, LinkProc=FileName;
let ServiceAbuse =
DeviceFileEvents
| where TimeGenerated > ago(Lookback)
| where InitiatingProcessFileName =~ "TSNxGService.exe"
| where FolderPath has_any (@"\Windows\System32\drivers\", @"\Windows\System32\config\", @"\Windows\SysWOW64\")
| where FolderPath !has "G Data"
| project ServiceTime=TimeGenerated, DeviceName, ActionType, FolderPath, ServiceAccount=InitiatingProcessAccountName;
LinkCreation
| join kind=leftouter ServiceAbuse on DeviceName
| extend Correlated = isnotnull(ServiceTime)
| project LinkTime, DeviceName, LinkAccount, LinkCmd, LinkProc, Correlated, ServiceTime, ActionType, FolderPath
| order by LinkTime desc
Velociraptor VQL
Use this hunt artifact to sweep the fleet for existing junctions and symlinks inside G DATA directories placed by anything other than SYSTEM — evidence of pre-staged exploitation even before service interaction occurs.
-- Hunt for suspicious reparse points (junctions/symlinks) in G DATA directories
-- consistent with CVE-2026-19776 link-following staging (ZDI-26-1030)
LET paths = SELECT FullPath, Name, Mode, Mtime
FROM glob(globs=['C:/ProgramData/G Data/**', 'C:/Program Files/G Data/**', 'C:/Program Files (x86)/G Data/**'])
WHERE Mode =~ 'L'
SELECT FullPath AS SuspiciousLinkPath,
Name AS LinkName,
Mode AS FileMode,
Mtime AS ModifiedTime,
hostname() AS Host
FROM paths
Remediation / Verification Script
The following PowerShell identifies G DATA installations, enumerates existing reparse points in G DATA paths (potential staged links), enables targeted file-system auditing on those directories, and reports service state. Run it as Administrator, fleet-wide via your RMM or GPO startup script.
# CVE-2026-19776 (ZDI-26-1030) - G DATA TSNxGService Link Following
# Verification and hardening script - run elevated on endpoints
$report = [ordered]@{}
# 1. Confirm G DATA Total Security presence and version
$gd = Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*',
'HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*' -ErrorAction SilentlyContinue |
Where-Object { $_.DisplayName -match 'G DATA' } |
Select-Object DisplayName, DisplayVersion, InstallLocation
$report.GDataInstalls = $gd
if (-not $gd) {
Write-Output '[*] No G DATA installation found. Nothing to do.'
exit 0
}
Write-Output '[!] G DATA detected - host is potentially exposed to CVE-2026-19776 (unpatched):'
$gd | Format-Table -AutoSize
# 2. Enumerate existing reparse points (junctions/symlinks/hardlinks) in G DATA paths
$gdPaths = @('C:\ProgramData\G Data', 'C:\Program Files\G Data', 'C:\Program Files (x86)\G Data') |
Where-Object { Test-Path $_ }
$suspicious = foreach ($p in $gdPaths) {
Get-ChildItem -Path $p -Recurse -Force -ErrorAction SilentlyContinue |
Where-Object { $_.Attributes -band [IO.FileAttributes]::ReparsePoint } |
Select-Object FullName, LinkType, Target, LastWriteTime
}
$report.StagedLinks = $suspicious
if ($suspicious) {
Write-Output '[CRITICAL] Reparse points found in G DATA directories - investigate for staged link-following exploitation:'
$suspicious | Format-List
} else {
Write-Output '[+] No reparse points detected in G DATA paths.'
}
# 3. Check TSNxGService state
$svc = Get-Service -ErrorAction SilentlyContinue | Where-Object { $_.Name -match 'TSNxG|GData' }
$report.Services = $svc | Select-Object Name, Status, StartType
$svc | Format-Table Name, Status, StartType -AutoSize
# 4. Enable Object Access / File System auditing on G DATA directories to capture
# privileged service file operations redirected outside expected scope
foreach ($p in $gdPaths) {
$acl = Get-Acl $p
$rule = New-Object System.Security.AccessControl.FileSystemAuditRule(
'Everyone', 'Write,Delete,ChangePermissions,TakeOwnership',
'ContainerInherit,ObjectInherit', 'None', 'Success')
$acl.AddAuditRule($rule)
Set-Acl -Path $p -AclObject $acl
Write-Output "[+] Success auditing enabled on: $p"
}
# Ensure the File System audit policy subcategory is on
auditpol /set /subcategory:"File System" /success:enable | Out-Null
Write-Output '[+] File System success auditing enabled. Forward Event ID 4663 filtered on G DATA paths and TSNxGService.exe to your SIEM.'
# 5. Output summary JSON for RMM/SIEM ingestion
$report | ConvertTo-Json -Depth 4
Remediation
There is no patch as of this writing. Until G DATA ships a fix, apply layered compensating controls:
- Track the vendor fix aggressively. Monitor G DATA's security advisories and the ZDI-26-1030 advisory page for patch publication. Given ZDI's disclosure timeline, engage your G DATA account or distribution channel directly and demand a patch ETA and private hotfix availability. When the update ships, treat deployment as an emergency change — this is an unpatched AV privilege escalation; do not let it sit in a standard 30-day patch cycle.
- Deploy the detections above fleet-wide — link/junction creation in security-product paths and privileged-service file operations outside expected directories are near-zero-noise signals. Forward file-system auditing (Event ID 4663) on G DATA directories to your SIEM immediately using the script above.
- Restrict local code execution prerequisites. The attacker must first execute low-privileged code. Enforce application control (WDAC/AppLocker) on standard users, block unsigned binaries and script interpreters for non-admin roles, and ensure phishing-resistant controls at the email/web boundary to shrink the initial-foothold surface this bug chains with.
- Constrain junction/symlink abuse. Where operationally feasible, enforce the "symlink evaluation" hardening (via
fsutil behavior set symlinkevaluation) and auditSeCreateSymbolicLinkPrivilegeassignments — standard users should not hold this privilege in enterprise builds. - Hunt retroactively. Run the Velociraptor artifact and KQL query over the last 30–90 days. A pre-staged junction sitting in a G DATA directory today is tomorrow's SYSTEM shell.
- Watch CISA KEV. If CVE-2026-19776 is added, BOD 22-01 remediation deadlines apply to federal agencies, and all organizations should treat KEV listing as a forcing function for emergency mitigation.
- Consider compensating EDR coverage. If G DATA is your sole endpoint control, deploy an independent EDR sensor in parallel during the exposure window — an attacker who escalates to SYSTEM through the AV can potentially tamper with the AV itself, so out-of-band telemetry is your safety net.
The Bottom Line
CVE-2026-19776 is exactly the kind of vulnerability that doesn't make headlines until it shows up in a ransomware intrusion timeline. It is unpatched, low-complexity, and lives inside the one process on your endpoints that everything else trusts. The exploitation window is open right now. Get the auditing enabled, get the detections deployed, hunt for staged reparse points, and pressure the vendor for a fix date. When the patch lands, push it like a KEV emergency — because by then, it may already be one.
Related Resources
Security Arsenal Penetration Testing Services AlertMonitor Platform Book a SOC Assessment vulnerability-management Intel Hub
Is your security operations ready?
Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.