By weakness (CWE)

CWE-325: related vulnerabilities

CVEs classified under CWE-325. Understanding the weakness class helps prioritize systemic fixes over one-off patches.

5 published vulnerabilities

• CVE-2026-45445HIGH 7.5

  OpenSSL has a flaw in its AES-OCB encryption handling when applications use the lower-level one-shot EVP_Cipher() interface. The supplied encryption key (IV) is ignored, causing every message encrypted under the same key to use an identical effective nonce. This breaks the confidentiality guarantee of the encryption and, worse, enables attackers to forge authentication tags—meaning they can create fake encrypted messages that will be accepted as legitimate. The issue only affects applications that directly use the EVP_Cipher() one-shot API with AES-OCB; applications using the recommended streaming interface or TLS connections are not at risk.

• CVE-2026-49440HIGH 7.4

  Deno's prime number validation function contains a critical flaw that allows composite numbers to be incorrectly identified as prime. When developers use the default settings, the checkPrime() and checkPrimeSync() functions skip cryptographic validation rounds entirely, relying only on a basic divisibility check against small primes. This means a number that is actually the product of two larger primes can be falsely reported as prime, potentially compromising cryptographic operations that depend on genuine prime generation.

• CVE-2026-0420MEDIUM 5.9

  NETGEAR's ReadyCloud client application contains a flaw in how it validates TLS certificates, the security handshakes that protect encrypted connections. An attacker positioned on the network path between a user and NETGEAR's servers could intercept and read sensitive data transmitted by the app—such as account credentials or cloud sync information—without being detected. The vulnerability requires specific network conditions to exploit but poses a real confidentiality risk for users relying on ReadyCloud for remote device management.

• CVE-2026-45446MEDIUM 4.8

  OpenSSL's implementations of two advanced encryption modes, AES-SIV and AES-GCM-SIV, contain a flaw in how they verify message authenticity when the encrypted content is empty. An attacker can craft a fraudulent message with attached metadata (AAD) and an empty ciphertext that will pass authentication checks without knowing the encryption key. This is only exploitable in custom applications that implement their own protocols using OpenSSL's EVP interface and skip processing when receiving empty ciphertext.

• CVE-2026-42770LOW 3.7

  A weakness in OpenSSL's handling of X9.42 Diffie-Hellman key exchanges allows a malicious peer to forge domain parameters in a way that bypasses security validation. Specifically, when checking that a peer's public key belongs to the correct mathematical subgroup, OpenSSL uses the peer's own parameters instead of verifying against the local key's parameters. An attacker can exploit this to gradually recover fragments of a victim's private key through repeated key exchange attempts, ultimately reconstructing the entire key via mathematical combination. However, the practical risk is limited to specific scenarios: principally Certificate Management Protocol (CMP) deployments where a Certification Authority or Registration Authority maintains long-lived X9.42 DHX keys, and custom enterprise or government applications using static DHX keys in interactive protocols.