CVE Watch8 de out. de 2026

CVE-2018-0734

The OpenSSL DSA signature algorithm has been shown to be vulnerable to a timing side channel attack. An attacker could use variations in the

CVSS

5.9

Média

EPSS

12.2%

p96

KEV

—

Exploit Today

0-100

Publicado: 30 de out. de 2018 · Última mod.: 8 de out. de 2026 · CWE-327

EPSS · 30d

12.2%EPSS · 30 dias12.2%

2026-10-142026-11-11

Descrição técnica

The OpenSSL DSA signature algorithm has been shown to be vulnerable to a timing side channel attack. An attacker could use variations in the signing algorithm to recover the private key. Fixed in OpenSSL 1.1.1a (Affected 1.1.1). Fixed in OpenSSL 1.1.0j (Affected 1.1.0-1.1.0i). Fixed in OpenSSL 1.0.2q (Affected 1.0.2-1.0.2p).

Referências oficiais

CVEs relacionados

CVECVSSEPSSKEVRExploitTítuloMod.

CVE-2026-1135725.9 MÉD

45.4%

——14CAI Content Credentials is affected by a Use of a Broken or Risky Cryptographic Algorithm vulnerability that could result in a Security feature bypass. An attacker could leverage this vulnerability to bypass security measures and gain unauthorized write access. Exploit depends on conditions beyond the attacker's control. Exploitation of this issue does not require user interaction.2d CVE-2026-1181025.9 MÉD

40.9%

——12Use of a broken or risky cryptographic algorithm in SQL Server allows an unauthorized attacker to disclose information over a network.2d CVE-2026-1137636.3 MÉD

8.1%

——2Use of a broken or risky cryptographic algorithm in Windows DPAPI (Data Protection Application Programming Interface) allows an authorized attacker to elevate privileges locally.2d CVE-2026-112168—

0.0%

——0The Magistra software uses weak custom encryption, relies on an outdated compression algorithm to protect the database, and contains embedded secrets.3d CVE-2026-785376.8 MÉD

0.2%

——0IBM Guardium Key Lifecycle Manager 4.1, 4.1.1, 4.2, 4.2.1, 5.0, and 5.1 could allow a local attacker to obtain sensitive information due to the use of a weak cryptographic algorithm.3d CVE-2026-1186845.9 MÉD

8.2%

——2MONAI before 1.6.1 contains an insufficient integrity verification vulnerability in check_hash() that silently returns True when hash_val is None, with MD5 as the default hash type. Attackers performing man-in-the-middle or registry compromise can substitute bundles, datasets, or model archives downloaded without hashes, enabling malicious file delivery and potential code execution.8d