CVE-2026-133185
Description
A flaw was found in goproxy. A remote attacker can impersonate trusted hosts and intercept encrypted traffic due to a weak key generation vulnerability during certificate creation. The component improperly derives private keys for generated certificates using predictable public data. By obtaining the proxy Certificate Authority (CA) certificate and observing a single leaf certificate for a target host, an attacker can reproduce that host's private key and masquerade as the legitimate host to connecting clients.
Statement
A weak key generation vulnerability exists in goproxy within the NewCounterEncryptorRandFromKey function, where misuse of hash.Sum deterministically derives RSA and Ed25519 leaf certificate private keys from public data. By obtaining the proxy CA certificate and observing a single leaf certificate for a target host, a remote attacker can reconstruct that host's private key to impersonate the legitimate server and intercept or tamper with encrypted traffic from clients trusting the proxy CA.
Mitigation
Disable dynamic TLS man-in-the-middle (MITM) certificate generation in goproxy where full payload inspection is not strictly required, and restrict distribution of the proxy CA certificate exclusively to trusted, segmented client networks. Enforce strict network access controls to prevent untrusted parties from querying the proxy to harvest generated leaf certificates, and rotate the proxy CA keypair if exposure is suspected.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 7.4 | N/A | 7.4 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | High | N/A | High |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | High |
| Integrity Impact | High | N/A | High |
| Availability Impact | None | N/A | None |
Vector
Red Hat: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
cve.org: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Understanding the Weakness (CWE)
Access Control,Other
Technical Impact: Bypass Protection Mechanism; Other
If a PRNG is used incorrectly, such as using the same seed for each initialization or using a predictable seed, then an attacker may be able to easily guess the seed and thus the random numbers. This could lead to unauthorized access to a system if the seed is used for authentication and authorization.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.