G DATA Total Security denial of service via symlink in AVKProxy
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
G DATA Total Security is affected by a link-following flaw in its AVKProxy component, which is the G DATA ANTIVIRUS Proxy Service. A local attacker who can already run low-privileged code can abuse a symbolic link to make the service create a file, which can leave the system in a persistent denial-of-service state.
Written by a model
Original description
G DATA Total Security AVKProxy Link Following Denial-of-Service Vulnerability. This vulnerability allows local attackers to create a denial-of-service condition 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 G DATA ANTIVIRUS Proxy Service. By creating a symbolic link, an attacker can abuse the service to create a file. An attacker can leverage this vulnerability to create a persistent denial-of-service condition on the system. Was ZDI-CAN-28662.
What to do
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-19777 (G DATA Total Security AVKProxy Link Following Denial-of-Service 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-19777 (entry last updated 2026-11-20):
Affected:
- G DATA Total Security: versions 25.5.19.439
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-19777 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-19777 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-1029/
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-19777
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-19777"}.Affected versions
- G DATA Total Security25.5.19.439
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.1/10CVSS 6.1
- No patch5/5No patch listed yet
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 33 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 2
| Kind | Source |
|---|---|
| CVE record 1Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-19777 |
| Other links 1 | |
| Link | zerodayinitiative.com · advisories/ZDI-26-1029 |
Questions about CVE-2026-19777
Is CVE-2026-19777 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: cve.now feed data
Which versions are affected by CVE-2026-19777?
Total Security: version 25.5.19.439.
Source: cve.now feed data
Related
- CVE-2026-19776G DATA Total Security TSNxGService Link Following Local Privilege Escalation Vulnerability
- CVE-2026-13268G DATA Total Security Backup Service Link Following Local Privilege Escalation Vulnerability
- CVE-2024-30377G DATA Total Security Scan Server Link Following Local Privilege Escalation Vulnerability
- CVE-2024-1868G DATA Total Security Link Following Local Privilege Escalation Vulnerability
- CVE-2024-1867G DATA Total Security Link Following Local Privilege Escalation Vulnerability
- CVE-2023-42126G DATA Total Security GDBackupSvc Service Link Following Local Privilege Escalation Vulnerability
No corrections so far. Something wrong on this page? Report an error.