In `github.com/eclipse-keypont/crypto11/v2` versions `<= 2.0.0-rc8` (and the deprecated v1 module paths `github.com/eclipse-keypont/crypto11 <= 1.6.8`, `github.com/ThalesGroup/crypto11 <= 1.7.0-rc1` and `github.com/ThalesIgnite/crypto11 <= 1.2.5`), the `cipher.AEAD` returned by `SecretKey.NewGCM()` passes whatever nonce it is given straight to `CK_GCM_PARAMS` without checking its length against `NonceSize()`, and accepts an empty nonce. On a token that accepts a zero-length GCM IV — SoftHSM2 does — every `Seal` with an empty nonce encrypts under the same IV, reusing the keystream and exposing the GHASH authentication key, which allows forgeries. Separately, `Config.UseGCMIVFromHSM` sends a NULL IV with length zero to the token unless `GCMIVFromHSMControl.SupplyIvForHSMGCMEncrypt` is also set, so the token has nowhere to write the IV it generates: a `Seal` with a non-empty nonce panics after the plaintext has already been encrypted, and a `Seal` with an empty nonce returns ciphertext under an empty IV without error. On the v1 line HSM-IV mode additionally never copies the token-generated IV back to the caller, so the caller keeps its own nonce while the data was encrypted under another one.
CVE-2026-109140 is a vulnerability in NLnet Labs Krill where the encryption of login-session tokens reuses the same (key, nonce) pair after each restart. This occurs because the nonce is derived from a counter that resets to zero on every Krill restart, violating best practices for nonce usage in encryption.
CVE-2026-71884 is a vulnerability in Legion of the Bouncy Castle Inc.'s BC-LTS-JAVA library versions 2.73.4 up to but not including 2.73.13. The native one-shot CTR packet cipher implementation did not validate that the input length fit within the counter space derived from the IV, causing the counter to wrap and the keystream to repeat. This results in two segments of the ciphertext being encrypted under the same keystream, allowing plaintext recovery without the key. The issue affects the native one-shot path only; other implementations validate the counter range properly. The vulnerability has a high severity with a CVSS 4.0 score of 8.2.
CVE-2026-81341 is a vulnerability in wolfSSL Inc.'s wolfEngine before version 1.4.1 where the AES-CCM nonce for TLS 1.2 and DTLS 1.2 records is incorrectly sourced from a constant value rather than the TLS sequence number. This causes reuse of the same key and nonce pair across multiple records, weakening confidentiality and integrity. The issue affects only wolfEngine with AES-CCM cipher suites, which are not enabled by default and must be explicitly selected. TLS 1.3 and non-TLS uses are not affected.
wolfEngine versions up to 1.4.0 have a vulnerability in their AES-GCM implementation for TLS 1.2 and DTLS 1.2. The explicit 8-byte AES-GCM nonce is generated once per connection and not incremented per record, causing reuse of the key and nonce pair. This nonce reuse leaks the keystream and the GHASH authentication key, enabling attackers to forge authentication tags. AES-CCM, TLS 1.3, and non-TLS cipher uses are not affected. The vulnerability has a high severity with a CVSS score of 7.4.
wolfProvider versions up to 1.2.1 have a vulnerability where the 8-byte explicit AES-GCM nonce is generated once per connection and never incremented per record. This causes every TLS 1.2 and DTLS 1.2 AES-GCM record within a connection to be encrypted with the same key and nonce pair, leading to keystream disclosure and authentication tag forgery. AES-CCM, TLS 1.3, and non-TLS cipher uses are not affected.
CVE-2026-50577 is a vulnerability in fbeta-GmbH's ePA3-Service-OpenSource prior to version 1.3.0. The flaw involves reuse of AES-GCM nonce and key pairs due to a frozen client request counter, which leads to repeated nonces in encrypted responses. This allows an attacker to recover XORs of plaintexts and potentially sensitive patient health data. Additionally, the vulnerability enables recovery of the GHASH authentication key via the Joux forbidden attack, permitting message forgery and injection of malicious responses. The issue also weakens replay and ordering validation by failing to maintain the last response counter. The vulnerability is fixed in version 1.3.0.
Kong Event Gateway versions 1.0.0 through 1.1.1 and 1.2.0 have a vulnerability where key rotation is not enforced before reaching the NIST recommended usage limit for AES-GCM encryption keys with random nonces when AWS IAM encryption is enabled. This can lead to nonce reuse, increasing the risk of nonce collisions. An authorized consumer detecting such a collision could recover parts of plaintext from affected messages. Versions 1.1.2 and 1.2.1 address this issue by enforcing automatic key rotation before the usage limit is reached.
Cryptographic Issue when using a static initialization vector for AES-GCM key wrapping, which requires a unique value for each call to ensure security.
Apereo CAS 7.3.0 before 8.0.0-RC6 contains a cryptographic vulnerability that allows remote unauthenticated attackers to recover plaintext conversation state by exploiting AES-GCM initialization vector reuse across the server lifetime. Attackers can collect multiple client-side webflow execution tokens from the unauthenticated login page and perform known-plaintext analysis to decrypt the webflow conversation state due to keystream reuse caused by a fixed all-zero IV paired with the same encryption key.
Crypt::DSA versions before 1.21 for Perl contain a vulnerability where the nonce used in digital signatures is reused across multiple signatures. This reuse occurs because the nonce material is cached in the Key object and never cleared, causing identical nonce values in subsequent signatures. As a result, private keys can be recovered if the same key signs more than once. This vulnerability is classified as CWE-323 and has a critical severity with a CVSS score of 9.1.
Astro is a web framework. Astro versions prior to 6.1.10 used AES-GCM encryption to protect the confidentiality and integrity of server island props and slots parameters, but did not bind the ciphertext to its intended component or parameter type. An attacker could replay one component's encrypted props (p) value as another component's slots (s) value, or vice versa. Since slots contain raw unescaped HTML while props may contain user-controlled values, this could lead to XSS in applications. This occurs when the application uses server islands, two different server island components share the same key name for a prop and a slot, and an attacker has full control over the value of the overlapping prop (requires a dynamically rendered page). This vulnerability is fixed in 6.1.10.
CVE-2026-3559 is a high-severity vulnerability in the Philips Hue Bridge version 1.73.1973146020 that allows network-adjacent attackers to bypass authentication without any privileges. The flaw is due to the reuse of a static nonce in the SRP authentication mechanism of the HomeKit Accessory Protocol service, which listens on TCP port 8080 by default. This static nonce enables attackers to circumvent authentication controls, potentially gaining unauthorized access to the device. There is no indication that a patch or official fix is currently available. Exploits in the wild have not been reported as of the publication date.
Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution'), Use of Password Hash With Insufficient Computational Effort vulnerability in rustdesk-client RustDesk Client rustdesk, hbb_common on Windows, MacOS, Linux (Password security module, config encryption, machine UID modules) allows Retrieve Embedded Sensitive Data. This vulnerability is associated with program files hbb_common/src/password_security.Rs, hbb_common/src/config.Rs, hbb_common/src/lib.Rs (get_uuid), machine-uid/src/lib.Rs and program routines symmetric_crypt(), encrypt_str_or_original(), decrypt_str_or_original(), get_uuid(), get_machine_id().
This issue affects RustDesk Client: through 1.4.5. NOTE: some third parties have indicated that these details do not align with the Supplier's statements.
strongMan is a management interface for strongSwan, an OpenSource IPsec-based VPN. When storing credentials in the database (private keys, EAP secrets), strongMan encrypts the corresponding database fields. So far it used AES in CTR mode with a global database key. Together with an initialization vector (IV), a key stream is generated to encrypt the data in the database fields. But because strongMan did not generate individual IVs, every database field was encrypted using the same key stream. An attacker that has access to the database can use this to recover the encrypted credentials. In particular, because certificates, which have to be considered public information, are also encrypted using the same mechanism, an attacker can directly recover a large chunk of the key stream, which allows them to decrypt basically all other secrets especially ECDSA private keys and EAP secrets, which are usually a lot shorter. Version 0.2.0 fixes the issue by switching to AES-GCM-SIV encryption with a random nonce and an individually derived encryption key, using HKDF, for each encrypted value. Database migrations are provided to automatically re-encrypt all credentials.
hpke-js is a Hybrid Public Key Encryption (HPKE) module built on top of Web Cryptography API. Prior to version 1.7.5, the public SenderContext Seal() API has a race condition which allows for the same AEAD nonce to be re-used for multiple Seal() calls. This can lead to complete loss of Confidentiality and Integrity of the produced messages. This issue has been patched in version 1.7.5.
The AES key utilized in the pairing process between a lock using Sciener firmware and a wireless keypad is not unique, and can be reused to compromise other locks using the Sciener firmware.
Consensys Discovery versions less than 0.4.5 uses the same AES/GCM nonce for the entire session. which should ideally be unique for every message. The node's private key isn't compromised, only the session key generated for specific peer communication is exposed.