CWE-327: Weak Cryptography vulnerabilities

CVE-2026-113572 is a vulnerability in Adobe Content Credentials Rust SDK caused by the use of a broken or risky cryptographic algorithm. This flaw could allow an attacker to bypass security features and gain unauthorized write access without requiring user interaction. Exploitation depends on conditions beyond the attacker's control. The vulnerability has a medium severity rating with a CVSS score of 5.9.

CVE-2026-118102 is a vulnerability in Microsoft SQL Server 2017 (GDR) involving the use of a broken or risky cryptographic algorithm. This flaw allows an unauthorized attacker to disclose information over a network. The vulnerability affects multiple versions of SQL Server 2017 and later branches prior to specific fixed releases. Microsoft has issued official fixes for this vulnerability.

CVE-2026-113763 is a vulnerability in Microsoft Windows 10 Version 1607 and related builds involving the use of a broken or risky cryptographic algorithm in the Windows Data Protection API (DPAPI). This flaw allows an authorized local attacker to elevate privileges. The vulnerability has a medium severity rating with a CVSS score of 6.3. Official patches have been released to address this issue in multiple Windows 10 versions.

CVE-2026-112168 affects GALENO SISTEMI's MAGISTRA software version 3.12. The vulnerability involves the use of weak custom encryption, reliance on an outdated compression algorithm for database protection, and the presence of embedded secrets, leading to cleartext storage of sensitive information.

IBM 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.

CVE-2026-108015 is a critical vulnerability in HCLSoftware Notes Client caused by the compromise of private keys for eight eMudhra intermediate CA certificates. This weakness allows an unauthenticated network attacker to spoof server certificates and perform man-in-the-middle (MITM) attacks on outbound TLS connections, potentially intercepting or modifying sensitive data.

CVE-2026-108014 concerns the compromise of private keys for eight eMudhra intermediate CA certificates, affecting HCL Domino Server's certificate trust for outbound network requests. This vulnerability allows an unauthenticated network attacker to spoof server certificates and perform man-in-the-middle (MITM) attacks on outbound TLS connections, potentially intercepting or modifying data. The issue is classified under CWE-327 due to the use of broken or risky cryptographic algorithms. The vulnerability has a critical severity with a CVSS 4.0 score of 9.1.

IBM Cloud Pak System versions 2.3.6.0 and 2.3.6.1 use cryptographic algorithms that are weaker than expected. This weakness could allow an attacker to decrypt highly sensitive information. The vulnerability is identified as CWE-327, indicating the use of broken or risky cryptographic algorithms. The CVSS v3.1 base score is 5.9, reflecting a medium severity level. No public exploits or known active exploitation have been reported. The affected product is not a cloud service, and no patch or remediation details are provided in the available data.

IBM Concert versions 1.0 through 3.0.0 use cryptographic algorithms that are weaker than expected. This weakness could potentially allow an attacker to decrypt highly sensitive information. The vulnerability has a low CVSS score of 3.7, indicating limited impact and exploitability. No known exploits are reported in the wild, and no patches or fixes have been indicated.

Use of a broken or risky cryptographic algorithm in Windows Remote Desktop allows an unauthorized attacker to bypass a security feature over a network.

CVE-2026-102824 affects the Eugeny russh Rust SSH client and server library prior to version 0.63.0. The vulnerability arises from the hybrid ML-KEM 768 and X25519 key exchange implementation accepting an all-zero 32-byte peer X25519 public key. This causes the X25519 contribution to the combined shared secret to be zero, allowing a malicious peer to force the shared secret to depend solely on ML-KEM. This defeats the intended fallback protection of the hybrid exchange. The issue is fixed in russh version 0.63.0.

IBM Db2 Mirror for i 7.6, 7.5, and 7.4 could allow a local attacker to obtain sensitive information due to the use of the AES Electronic Codebook (ECB) mode for encryption.

Imprivata Enterprise Access Management (EAM) versions up to 26.2.6 use an RSA key pair for generating X.509 certificates that cannot be rotated after deployment. This practice of indefinite use of the same RSA key pair is against cryptographic best practices and results in inadequate encryption strength.

IBM Financial Transaction Manager (FTM) for RedHat OpenShift could allow a remote authenticated attacker to obtain sensitive information and forge authentication tags due to the use of hard-coded cryptographic keys and initialization vectors.

IBM Concert 1.0.0 through 3.0.0 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information.

IBM Cognos Analytics 12.1.0 through 12.1.3 FP1, and 12.0.4 through 12.0.4 FP2 could allow an attacker on a shared network to obtain sensitive information caused by insecure network communication.

IBM Cognos Analytics versions 12.0.4 and 12.1.0 contain a vulnerability due to failure to properly enable HTTP Strict Transport Security (HSTS). This weakness could allow a remote attacker to intercept sensitive information via man-in-the-middle techniques. The issue is classified under CWE-327 for use of a broken or risky cryptographic algorithm. The vulnerability has a medium severity with a CVSS score of 5.9.

Dell OpenManage Server Administrator, versions prior to 11.1.0.3, contains Use of a Broken or Risky Cryptographic Algorithm vulnerability. An unauthenticated attacker with remote access could potentially exploit this vulnerability, leading to Information disclosure.

Dell ECS versions 3.8.1.0 through 3.8.1.7, and Dell ObjectScale versions prior to 4.4.0.0, contains an Use of a Broken or Risky Cryptographic Algorithm vulnerability. A high privileged attacker with local access could potentially exploit this vulnerability, leading to Information exposure.