External risk intelligence

GnuPG for Windows DACL Inheritance Vulnerability Allows Code Execution.

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-118131

The vulnerability requires local access to the Windows file system to manipulate directory permissions and inject configuration files within the C:\ProgramData path. It is a client-side, local-privilege-escalation issue that is not reachable via the public internet.

Halo Surface Signal: 1 out of 5 — much less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

GnuPG for Windows has a critical vulnerability that allows low-privilege users to execute malicious code by manipulating configuration files. This issue arises from how permissions are managed on a common Windows directory, potentially enabling attackers to compromise user accounts.

  • Local users can inject malicious code.
  • Code execution in user's security context.
  • Confirm relevance and understand potential exposure.

Attack Path

How an attacker could exploit the issue

An attacker with basic user access on a Windows machine can exploit a weakness in how GnuPG handles file permissions. By creating a malicious configuration directory and files within a shared location, the attacker can trick GnuPG into running their code when the application starts. This could lead to the attacker gaining control of the victim's computer.

  • Local user access is required.
  • Attacker creates malicious GnuPG configuration.
  • Leads to code execution as the victim user.

Live Threat

Current exploitation, exposure, and threat context

A low-privilege attacker on Windows could create a malicious GnuPG configuration directory under `C:\ProgramData`, leading to code execution within the victim user's security context when GnuPG components process the injected files.

  • Code execution for victim user.
  • Attacker creates malicious config files.
  • Sensitive data access and modification.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in GnuPG for Windows, which allows for code execution via manipulated configuration files in a shared directory, likely falls under the responsibility of the Windows system administration or endpoint security teams. The first step is to identify all Windows systems with GnuPG installed, confirm if they are accessible to unprivileged users, and then determine the accountable owner for remediation or mitigation.

  • Own: Windows System Administrators.
  • Verify: GnuPG installation and user access.
  • Action: Plan controlled remediation.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is GnuPG and how is it used on Windows?

GnuPG (GNU Privacy Guard) is a widely used software suite for data encryption and digital signatures. It allows users to encrypt files and secure communications. On Windows, GnuPG components often rely on specific configuration files stored in system-wide directories to function correctly, ensuring that encryption settings and key management policies are applied consistently for users on that machine.

What does CVE-2026-118131 mean for GnuPG security?

This vulnerability involves a weakness in access control (CWE-732). Because the C:\ProgramData directory has permissive inheritance settings, an unprivileged user can create new subdirectories there. This flaw allows an attacker to plant fake configuration files that GnuPG components may trust, potentially leading the application to execute malicious commands using the victim's own permissions.

Can this be triggered by a remote attacker?

No. The vulnerability requires a user to already have local access to the Windows file system to create the malicious directory structure. A purely remote attacker who lacks an existing user account or local access on the machine cannot trigger this issue simply by sending data over a network or via email.

How relevant is this CVE for my environment?

According to Halo Surface Signal, this is very unlikely to be reachable from the public internet. The issue is a local-privilege-escalation risk, meaning it is most relevant on shared Windows systems where untrusted local users have access to the same machine where GnuPG is installed.

What should I do if I have GnuPG installed?

Start by identifying all Windows endpoints in your organization where GnuPG 2.5.21 is running. Coordinate with your endpoint security or system administration teams to review the folder permissions on C:\ProgramData. Ensure that standard users do not have permissions to create or modify directory structures that GnuPG relies upon for its operation.

References