G DATA Total Security local privilege escalation in backup service
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Summary
G DATA Total Security is affected by a local privilege escalation flaw in its Backup Service, which restores archives from an unsecured location. An attacker who already has low-privileged code execution on the system can use this to gain SYSTEM-level control, and the attack requires some user interaction.
Written by a model
Original description
G DATA Total Security Backup Service Uncontrolled Search Path Element 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 Backup Service. The service restores archives from an unsecured location. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code in the context of SYSTEM. Was ZDI-CAN-28666.
What to do
Check whether your setup matches what the bug needs.
Attacker must first be able to execute low-privileged code on the target system. The Backup Service restores archives from an unsecured location.Workaround: The checked facts name no workaround. Because the issue involves the Backup Service restoring archives from an unsecured location, follow the vendor's guidance on securing that restore location until a fix is available.
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-19779 (G DATA Total Security Backup Service Uncontrolled Search Path Element 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-19779 (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):
- Attacker must first be able to execute low-privileged code on the target system. (source: https://www.zerodayinitiative.com/advisories/ZDI-26-1028/)
- The Backup Service restores archives from an unsecured location. (source: https://www.zerodayinitiative.com/advisories/ZDI-26-1028/)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, low-privilege login, a user action.
CISA KEV: CVE-2026-19779 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-19779 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-1028/
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-19779
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-19779"}.Affected versions
- G DATA Total Security25.5.19.439
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.3/10CVSS 7.3
- No patch5/5No patch listed yet
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 27 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
Evidence 2
| Kind | Source |
|---|---|
| CVE record 1Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-19779 |
| Other links 1 | |
| Link | zerodayinitiative.com · advisories/ZDI-26-1028 |
Questions about CVE-2026-19779
Is CVE-2026-19779 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
What does this mean?
A local attacker who can already run low-privileged code can escalate privileges and execute arbitrary code in the context of SYSTEM. The Backup Service restores archives from an unsecured location, which is the flaw this bug exploits.
Source: zerodayinitiative.com
Which versions are affected by CVE-2026-19779?
Total Security: version 25.5.19.439.
Source: cve.now feed data
Am I affected, and how do I check?
The checked facts list no affected version ranges for G DATA Total Security. The affected setup is the Backup Service restoring archives from an unsecured location, so check the installed Total Security version and the vendor's advisory for the listed versions.
Source: zerodayinitiative.com
How do I fix CVE-2026-19779?
The checked facts name no fixed version and no patch identifiers, so no upgrade target can be given. Check the vendor's advisory for an update.
Source: zerodayinitiative.com
What if there's no patch?
The checked facts name no workaround. Because the issue involves the Backup Service restoring archives from an unsecured location, follow the vendor's guidance on securing that restore location until a fix is available.
Source: zerodayinitiative.com
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.