CVE-2026-115407Eclipse Foundation
NVD
Vulnerability Summary
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.
CVSS v4.0 Base Metrics — Score 9.1 (CRITICAL)
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NAttack VectorNetwork
Attack ComplexityHigh
Attack RequirementsNone
Privileges RequiredNone
User InteractionNone
Confidentiality (Vulnerable System)High
Integrity (Vulnerable System)High
Availability (Vulnerable System)None
Confidentiality (Subsequent System)None
Integrity (Subsequent System)None
Availability (Subsequent System)None
Affected & Patched Versions
- Eclipse Foundation <= 2.0.0-rc8
- Eclipse Foundation <= 1.6.8
- Eclipse Foundation <= 1.7.0-rc1
- Eclipse Foundation <= 1.2.5
- Eclipse Foundation 2.0.0-rc8
- Eclipse Foundation 1.6.8
- Eclipse Foundation 1.7.0-rc1
- Eclipse Foundation 1.2.5
What to do
Plan remediation soon. No exploitation is confirmed yet, but the severity is critical.
- Check whether you run Eclipse Foundation and which version.
- Update to a patched version listed above, then confirm the new version.
Timeline
- Nov 20, 2026Published
- Nov 20, 2026Record last modified
Score, severity and exploitation changes are tracked from the day Watchtower started logging them.
Get notified about new Eclipse Foundation CVEsYou are reading CVE-2026-115407. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alertsMore Eclipse Foundation CVEs
External References
Data last checked: Nov 21, 2026 12:07 UTC