CVE-2026-133185: critical vulnerability in elazarl goproxy
Elazarl goproxy before 1.9.4 Predictable MITM Leaf Certificate Private Keys
Published
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
48Vexday Risk Score
No sign of exploitation. It has a public proof of concept.
ssvc Attendcvss 9.1epss 0.3%
from disclosure to weaponsame day
Published on NVDNov 19
1st PoCNov 19
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.
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
Affected products
elazarl · goproxypublic PoCs found — 1
githubgithub.com/LLCForge/CVE-2026-133185★ 0⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.
References
https://github.com/elazarl/goproxyhttps://github.com/elazarl/goproxy/blob/v1.9.3/internal/signer/counterecryptor.go#L37-L44https://github.com/elazarl/goproxy/commit/c150a338c02550eedace75f4baad4f73c0605b3chttps://github.com/elazarl/goproxy/pull/822https://github.com/elazarl/goproxy/releases/tag/v1.9.4