External risk intelligence

Eclipse Crypto11 GCM nonce vulnerability allows forgeries.

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-115407

This is a low-level cryptographic library used by developers to interface with Hardware Security Modules (HSMs) or software tokens. It is not an internet-facing service, application, or gateway. While it may be included in applications that are network-reachable, the library itself operates as an internal component and does not have inherent public network exposure.

Halo Surface Signal: 2 out of 5 — less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory describes a flaw in a cryptographic library that could allow forgeries if an empty nonce is used during encryption. The issue stems from the library's handling of nonces, which are unique values used in encryption to ensure security.

  • Library flaw can lead to data forgeries.
  • Affects cryptographic operations relying on nonces.
  • Confirm relevance and exposure of this library.

Attack Path

How an attacker could exploit the issue

An attacker could compromise the security of data encrypted using the vulnerable crypto11 library by exploiting flaws in how it handles initialization vectors (IVs) for GCM mode encryption. If the library is used with a token that permits zero-length IVs, an attacker could cause the reuse of encryption keys, leading to the exposure of authentication keys and enabling message forgeries. Additionally, issues with how the library manages IVs generated by hardware security modules could lead to data being encrypted with incorrect or missing IVs, further compromising security.

  • Entry Condition: Network access to a vulnerable application.
  • Trigger Point: Encrypting data with an empty nonce.
  • Resulting Risk: Forgery of encrypted messages.

Live Threat

Current exploitation, exposure, and threat context

When a supported token, such as SoftHSM2, is configured to accept a zero-length nonce, an attacker could exploit this by reusing the same nonce for multiple encryption operations. This reuse can expose the authentication key, potentially allowing forgeries of encrypted data. Additionally, when a non-empty nonce is used, the system may panic after encryption, leading to unrecoverable data.

  • Encrypted data integrity and confidentiality.
  • Reusing nonces or providing zero-length nonces.
  • Unauthorized data modification or exposure.

Operational Fix

Recommended remediation, mitigation, and detection steps

The `crypto11` library, used for cryptographic operations with Hardware Security Modules (HSMs), is impacted by a nonce length validation vulnerability. Application owners and platform teams responsible for integrating this library need to identify all deployments, confirm their reachability and criticality, and then coordinate with vendor-management teams if a specific HSM product is involved. The first practical step is to enumerate all instances of the affected library, assess their exposure, and plan remediation within maintenance windows.

  • Application owners should own the issue.
  • Verify nonce handling and HSM configurations.
  • Plan coordinated remediation or vendor engagement.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the crypto11 library used for?

The crypto11 library is a specialized software component that enables developers to perform cryptographic operations by interfacing directly with Hardware Security Modules (HSMs) or software-based tokens like SoftHSM2. It acts as a bridge, allowing applications to securely manage keys and perform tasks like encryption and decryption using the high-security capabilities of these physical or virtual devices.

What does CVE-2026-115407 mean for encryption security?

This vulnerability, involving Improper Validation of Array Index and Reuse of Nonce (CWE-20, CWE-323, CWE-1204), occurs when the library fails to verify nonce lengths during encryption. If an empty nonce is accepted, the system reuses the same keystream for multiple operations. This exposes the underlying GHASH authentication key, which effectively breaks the security of the encryption and allows an attacker to create forged data that appears authentic.

How can an attacker trigger this vulnerability?

An attacker needs an application to perform encryption using a vulnerable version of the library while connected to a token that permits zero-length initialization vectors (IVs), such as SoftHSM2. The flaw is not triggered when using non-empty nonces correctly, although certain configurations may cause system crashes in those instances. The primary danger arises specifically when the system is directed to use an empty nonce, leading to predictable and insecure encryption.

Is my system at risk according to Halo Surface Signal?

According to Halo Surface Signal, this component is considered unlikely to be directly reachable. Because crypto11 is a low-level library integrated into internal application logic rather than an internet-facing gateway or standalone service, it typically lacks public network exposure. However, if your specific application exposes interfaces that process user-supplied data through this library, the internal risk remains relevant.

What should I do if I use crypto11 in my software?

Start by auditing your codebase to identify all locations where the affected crypto11 library versions are imported. Once mapped, verify whether your HSM or token configuration permits zero-length IVs. Coordinate with your development and platform teams to prioritize updates for any applications using this library, treating the integration point as a high-priority item for your next scheduled maintenance window.

References