External risk intelligence

Goproxy Predictable Private Key Generation Allows Impersonation

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-133185

Goproxy is a library commonly used to build HTTP/HTTPS proxy servers and intercepting proxies. These tools are frequently deployed as network-facing gateways or infrastructure services to manage, monitor, or filter web traffic, making them reachable via the network by design.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory concerns a vulnerability in goproxy, a technology used for proxying network traffic. The issue allows an attacker, with specific technical knowledge, to potentially impersonate legitimate hosts by recreating private keys used for secure communication. The main concern is confirming if this technology is in use and assessing potential exposure.

  • Predictable keys allow impersonation.
  • Vital for network traffic security.
  • Confirm usage and assess exposure.

Attack Path

How an attacker could exploit the issue

An attacker could impersonate a trusted host by exploiting a weakness in how the goproxy software generates private keys for security certificates. If an attacker can obtain the proxy's certificate authority (CA) certificate and one of its active leaf certificates, they may be able to recreate the private key for that specific host's certificate. This allows the attacker to then impersonate that host to any clients that trust the proxy's CA, potentially leading to man-in-the-middle attacks or other forms of eavesdropping and manipulation of traffic.

  • Requires CA and leaf certificates.
  • Predictable key generation is triggered.
  • Impersonate trusted hosts to clients.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, an attacker with the CA certificate and a leaf certificate could regenerate a host's private key. This could allow them to impersonate the host to clients that trust the proxy's CA.

  • Leaf certificate private keys at risk.
  • Attacker regenerates keys using public data.
  • Impersonation of trusted hosts to clients.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in GoProxy affects its ability to securely generate private keys for leaf certificates. Real-world responsibility likely falls to the platform or infrastructure teams managing proxy services, or potentially application owners if GoProxy is embedded within a specific application. The first practical step is to identify all GoProxy instances, determine their exposure and criticality, and locate the accountable owner for remediation planning.

  • Platform or application owners
  • Verify GoProxy instance reachability and criticality
  • Plan and coordinate secure key generation fix

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 Goproxy?

Goproxy is a library written in Go used by developers to build HTTP and HTTPS proxy servers. It acts as an intermediary, allowing applications to intercept, inspect, and modify web traffic. Because it is often embedded into infrastructure services or network gateways to manage traffic flows, it is commonly found running as a foundational component in internal or public-facing network environments.

What does CVE-2026-133185 mean by weak key generation?

This vulnerability, classified as CWE-337 (Predictable Seed in Pseudo-Random Number Generator), occurs because Goproxy uses a flawed method to derive cryptographic keys. Instead of creating unique, high-entropy private keys for HTTPS certificates, it generates them from predictable public data. This weakness allows an attacker to mathematically derive the private key of a certificate if they have access to the proxy's CA certificate and a sample leaf certificate.

When does this vulnerability get triggered?

The issue is triggered when an attacker possesses both the proxy's Certificate Authority (CA) certificate and at least one observed leaf certificate generated by that proxy. Simply running the software does not automatically trigger the bug; the attacker must have these specific pieces of public information to perform the key regeneration. If the proxy does not perform dynamic certificate signing or uses a different, secure key generation method, this specific flaw may not apply.

Why does Halo Surface Signal categorize this as external?

Halo Surface Signal labels this as external because Goproxy is frequently deployed as a network-facing gateway or infrastructure service. Since these proxies are designed to receive and filter web traffic, they are often reachable over the network. If your proxy instance is exposed to the internet, an attacker could potentially gain the necessary certificates to impersonate hosts, making the risk profile significantly higher than an isolated internal system.

How do I respond if I am running Goproxy?

Your first step is to identify all software and services in your environment that utilize the Goproxy library. Once located, verify if the instances are configured to perform certificate interception, as this is the primary context for the vulnerability. Work with your infrastructure or application teams to plan an update to version 1.9.4 or later, which contains the fix for the predictable key generation logic.

References