CVE-2026-133185 json
Elazarl goproxy before 1.9.4 Predictable MITM Leaf Certificate Private Keys
published 15h ago modified 10h ago also EUVD-2026-130067
- cvss
- 9.1
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- elazarl goproxy 1.9.4
- github.com/elazarl/goproxy@c150a33 commit
- github.com/elazarl/goproxy#822 pull request
- github.com/elazarl/goproxy/releases/tag/v1.9.4 release
Is CVE-2026-133185 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 10h ago
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 9.1 | 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 |
| CNA | 3.1 | 7.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |
Affected products
- elazarl goproxy
Classification
- Weakness
-
- CWE-337 Predictable Seed in Pseudo-Random Number Generator (PRNG)
References
-
github.com
/elazarl/goproxy/pull/822
issue-tracking, patch
-
github.com
/elazarl/goproxy/commit/c150a338c02550eedace75f4baad4f73c0605b3c
patch
-
github.com
/elazarl/goproxy/releases/tag/v1.9.4
release-notes
-
github.com
/elazarl/goproxy/blob/v1.9.3/internal/signer/counterecryptor.go#L37-L44
technical-description
-
github.com
/elazarl/goproxy
product
-
vulncheck.com
/advisories/elazarl-goproxy-before-1.9.4-predictable-mitm-leaf-certificate-private-keys
third-party-advisory
Sources
- CVE List CVE-2026-133185
- NVD CVE-2026-133185
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.