CVE-2026-21907 is a medium severity vulnerability in Juniper Networks Junos Space affecting versions before 24.1R5. It involves the use of static key ciphers in the TLS/SSL server, which are considered broken or risky cryptographic algorithms. These static key ciphers reduce the confidentiality of data by allowing potential on-path attackers to decrypt traffic and do not support Perfect Forward Secrecy (PFS), compromising long-term confidentiality. The vulnerability does not affect integrity or availability and requires no authentication or user interaction but has a high attack complexity. No known exploits are currently reported in the wild. European organizations using Junos Space for network management should prioritize upgrading to versions 24.1R5 or later to mitigate this risk. Countries with significant Juniper Networks deployments, such as Germany, France, and the UK, are more likely to be impacted due to their extensive telecommunications and enterprise infrastructure. Mitigation involves disabling static key ciphers and enabling PFS-capable cipher suites, alongside applying vendor patches once available.
CVE-2025-68702 is a high-severity vulnerability in the samrocketman Jervis library, used for Job DSL plugin scripts and Jenkins shared pipeline libraries. The issue arises from incorrect padding in cryptographic operations where padLeft(32, '0') is used instead of padLeft(64, '0') to handle SHA-256 hashes, which are 32 bytes or 64 hex characters long. This improper padding leads to the use of a broken or risky cryptographic algorithm (CWE-327), potentially weakening the security of cryptographic functions within affected Jenkins pipelines. The vulnerability affects all Jervis versions prior to 2.2 and does not require authentication or user interaction to exploit, with a CVSS 4.0 score of 8.7 indicating high severity. Although no known exploits are currently in the wild, the flaw could allow attackers to compromise the integrity of pipeline scripts or related secrets. The issue is fixed in version 2.2 of Jervis.
CVE-2025-68701 is a high-severity cryptographic vulnerability in the Jervis library used for Jenkins Job DSL and shared pipeline scripts. Versions prior to 2.2 use a deterministic AES initialization vector (IV) derived from a passphrase, which weakens encryption by making ciphertext patterns predictable and susceptible to cryptanalysis. This flaw allows attackers to potentially recover sensitive data or compromise the confidentiality of encrypted information without requiring authentication or user interaction. The vulnerability has a CVSS 4.0 base score of 8.7, indicating a network-exploitable issue with high impact on confidentiality. The issue is fixed in Jervis version 2.2. European organizations relying on Jenkins automation with Jervis versions before 2.
CVE-2025-68931 is a high-severity vulnerability affecting versions of the samrocketman jervis library prior to 2.2. The issue arises from the use of AES encryption in CBC mode with PKCS5 padding without proper authentication, making it vulnerable to padding oracle attacks and ciphertext manipulation. This improper authentication flaw (CWE-287) combined with weak cryptographic usage (CWE-327) allows attackers to decrypt or alter encrypted data without authorization. The vulnerability requires no authentication or user interaction and can be exploited remotely, posing a significant risk to confidentiality and integrity. The flaw is fixed in version 2.2 of jervis. European organizations using Jenkins pipelines or Job DSL scripts that incorporate jervis versions before 2.2 could face data compromise or pipeline manipulation. Mitigation involves upgrading to jervis 2.
Jervis is a library for Job DSL plugin scripts and shared Jenkins pipeline libraries. Prior to 2.2, Jervis uses PKCS1Encoding which is vulnerable to Bleichenbacher padding oracle attacks. Modern systems should use OAEP (Optimal Asymmetric Encryption Padding). This vulnerability is fixed in 2.2.
libtpms, a library that provides software emulation of a Trusted Platform Module, has a flaw in versions 0.10.0 and 0.10.1. The commonly used integration of libtpms with OpenSSL 3.x contained a vulnerability related to the returned IV (initialization vector) when certain symmetric ciphers were used. Instead of returning the last IV it returned the initial IV to the caller, thus weakening the subsequent encryption and decryption steps. The highest threat from this vulnerability is to data confidentiality. Version 0.10.2 fixes the issue. No known workarounds are available.
A vulnerability in the SSH server of TP-Link TL-WR820N v2.80 allows the use of a weak cryptographic algorithm, enabling an adjacent attacker to intercept and decrypt SSH traffic. Exploitation may expose sensitive information and compromise confidentiality.
CVE-2025-14764 is a medium-severity vulnerability in the Amazon S3 Encryption Client for Go involving the use of a broken or risky cryptographic algorithm due to missing cryptographic key commitment. This flaw allows a user with write access to an S3 bucket to introduce a new encrypted data key (EDK) that decrypts to different plaintext when the encrypted data key is stored in an instruction file rather than S3 metadata. The vulnerability does not impact confidentiality but can compromise data integrity by enabling unauthorized data manipulation. Exploitation requires network access, low privileges (write access), and no user interaction, with a CVSS score of 5.3. AWS has addressed this issue in version 4.0 or later of the S3 Encryption Client for Go. European organizations using vulnerable versions should upgrade promptly to prevent potential data integrity attacks, especially those relying on instruction file storage for encrypted data keys. Countries with significant AWS usage and cloud adoption, such as Germany, the UK, France, and the Netherlands, are most likely to be affected.
CVE-2025-14763 is a medium severity vulnerability in the Amazon S3 Encryption Client for Java prior to version 4.0.0. It involves the use of a broken or risky cryptographic algorithm due to missing cryptographic key commitment. This flaw allows a user with write access to an S3 bucket to introduce a new encrypted data key (EDK) that decrypts to different plaintext when the encrypted data key is stored in an instruction file rather than in S3's metadata. The issue is fixed in version 4.0.0 and later.
CVE-2025-14762 is a medium-severity vulnerability in the AWS SDK for Ruby involving the use of a broken or risky cryptographic algorithm. The issue arises from missing cryptographic key commitment when encrypted data keys (EDKs) are stored in an "instruction file" rather than S3 metadata. This flaw allows a user with write access to an S3 bucket to introduce a malicious EDK that decrypts to different plaintext, potentially compromising data integrity. Exploitation requires network access, low privileges, and no user interaction, but has a high impact on integrity without affecting confidentiality or availability. AWS has addressed this vulnerability in SDK version 1.208.0 and later. European organizations using the AWS SDK for Ruby, especially those heavily reliant on S3 for encrypted data storage, should prioritize upgrading to mitigate risks. Countries with significant cloud adoption and AWS usage, such as Germany, the UK, France, and the Netherlands, are most likely to be affected. The vulnerability does not appear to be exploited in the wild yet, but the risk of data tampering warrants prompt remediation.
CVE-2025-14761 is a medium-severity vulnerability in the AWS SDK for PHP involving the use of a broken or risky cryptographic algorithm. The issue arises from a missing cryptographic key commitment when encrypted data keys (EDKs) are stored in an instruction file rather than S3 metadata. This flaw allows a user with write access to an S3 bucket to introduce a malicious EDK that decrypts to different plaintext, potentially compromising data integrity. The vulnerability does not impact confidentiality or availability directly and requires low privileges but high attack complexity. No known exploits are currently reported in the wild. AWS has addressed this vulnerability in SDK version 3.368.0 and later. European organizations using AWS SDK for PHP with S3 encryption should prioritize upgrading to mitigate risks. Countries with significant AWS adoption and critical cloud infrastructure are more likely to be affected.
Missing cryptographic key commitment in the AWS SDK for C++ may allow a user with write access to the S3 bucket to introduce a new EDK that decrypts to different plaintext when the encrypted data key is stored in an "instruction file" instead of S3's metadata record.
To mitigate this issue, upgrade AWS SDK for C++ to version 1.11.712 or later
Missing cryptographic key commitment in the Amazon S3 Encryption Client for .NET may allow a user with write access to the S3 bucket to introduce a new EDK that decrypts to different plaintext when the encrypted data key is stored in an "instruction file" instead of S3's metadata record.
To mitigate this issue, upgrade Amazon S3 Encryption Client for .NET to version 3.2.0 or later.
Weak Encryption Algorithm in StreamPark, The use of an AES cipher in ECB mode and a weak random number generator for encrypting sensitive data, including JWT tokens, may have risked exposing sensitive authentication data
This issue affects Apache StreamPark: from 2.0.0 before 2.1.7.
Users are recommended to upgrade to version 2.1.7, which fixes the issue.
CVE-2025-66017 is a high-severity vulnerability affecting LFDT-Lockness's cggmp21 and cggmp24 cryptographic libraries. The flaw involves the use of presignatures in versions cggmp21 <= 0.6.3 and cggmp24 0.7.0-alpha.1, which significantly reduces the security of the ECDSA threshold signature scheme (TSS) implementation. This vulnerability stems from the use of a broken or risky cryptographic algorithm (CWE-327), potentially allowing attackers to compromise signature integrity. The issue is addressed in cggmp24 version 0.7.
Inside Track / Entropy Derby is a research-grade horse-racing betting engine. Prior to commit 2d38d2f, the VDF-based timelock encryption system fails to enforce sequential delay against the betting operator. Bettors pre-compute the entire Wesolowski VDF and include vdfOutputHex in their encrypted bet ticket, allowing the house to decrypt immediately using fast proof verification instead of expensive VDF evaluation. This issue has been patched via commit 2d38d2f.
IBM Concert 1.0.0 through 2.0.0 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information.
CVE-2025-36161 is a medium severity vulnerability in IBM Concert versions 1.0.0 through 2.0.0, caused by the failure to properly enforce HTTP Strict-Transport-Security (HSTS). This misconfiguration allows remote attackers to perform man-in-the-middle (MitM) attacks to intercept sensitive information transmitted over HTTP. The vulnerability stems from the use of a broken or risky cryptographic approach, classified under CWE-327. Exploitation does not require authentication or user interaction but has a higher attack complexity due to network conditions. No known exploits are currently reported in the wild. European organizations using IBM Concert should prioritize patching or mitigating this issue to protect confidentiality.
The vulnerability, if exploited, could allow a miscreant with read
access to Edge Project files or Edge Offline Cache files to reverse
engineer Edge users' app-native or Active Directory passwords through
computational brute-forcing of weak hashes.
