goproxy predictable leaf certificate keys enable MITM
- Exploited
- No known exploitation
- Fix
- Fixed in 1.9.4
- Who is exposed
- Not reported
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
Original 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.
Who should check
Teams running elazarl goproxy (Go) before 1.9.4 as a MITM proxy whose CA is trusted by clients
“Goproxy before 1.9.4 contains a weak key generation vulnerability”
What to do
Upgrade to a fixed version: 1.9.4.
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-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"}.Affected versions
cve.now Index
- Exploitation0/40No signal
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach10/20Affects Go packages
- Severity10/10CVSS 9.1, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 82 if added to CISA KEV
- Would score about 77 if CISA's SSVC rates exploitation active
- Would score about 42 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Evidence 9
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133185 |
| Record | NVD · CVE-2026-133185 |
| Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | GitHub · LLCForge/CVE-2026-133185 · Repository |
| Other links 6 | |
| Patch | GitHub · elazarl/goproxy · Pull request #822 |
| Patch | GitHub · elazarl/goproxy · Commit c150a338 |
| Repository | GitHub · elazarl/goproxy · Release v1.9.4 |
| Repository | GitHub · elazarl/goproxy · internal/signer/counterecryptor.go · L37-L44 |
| Repository | GitHub · elazarl/goproxy · Repository |
| Link | vulncheck.com · advisories/elazarl-goproxy-before-1.9.4-predictable-mitm-leaf-certificate-private-keys |
Questions about CVE-2026-133185
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: cve.now feed data
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: vulncheck.com
Which versions are affected by CVE-2026-133185?
github.com/elazarl/goproxy (Go): before 1.9.4.
Source: cve.now feed data
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: vulncheck.com
How do I fix CVE-2026-133185?
Upgrade goproxy to 1.9.4, the fixed version.
Source: vulncheck.com
Related
- CVE-2023-37788goproxy v1.1 was discovered to contain an issue which can lead to a Denial of service (DoS) via unspecified vectors.
- CVE-2026-130778Incus before 7.6.0 Authentication Bypass via Unverified Client Certificate Chains
- CVE-2026-130786Incus before 7.6.0 LXC Configuration Injection via OCI Image Config
- CVE-2026-130784Incus before 7.6.0 Authorization Bypass via Default Project Resource Inheritance
- CVE-2026-130780Incus before 7.6.0 Path Traversal via Dependent Volumes in Migration
- CVE-2026-130783Incus before 7.6.0 Token Exposure and Missing Authorization via Operation Events
No corrections so far. Something wrong on this page? Report an error.