Skip to main content
Menu
CVEs

Eclipse Foundation message forgery and decryption via GCM nonce handling

CVE-2026-115407Published , updated

9.1CriticalCNA
Exploited
No known exploitation
Fix
Fix or patch referenced
Who is exposed
Not reported

Summary

Several Go modules for the crypto11 library are affected, including github.com/eclipse-keypont/crypto11/v2 from the Eclipse Foundation and the older ThalesGroup and ThalesIgnite crypto11 module paths. Remotely, without logging in or any user action, an attacker can forge messages and read encrypted data, because the library does not check GCM nonce length and can end up reusing the same IV.

Written by a model

Original description

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.

What to do

Apply the patch listed under Evidence.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-115407 (In `github.com/eclipse-keypont/crypto11/v2` versions `<= 2.0.0-rc8` (and the deprecated v1 module paths…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-115407 (entry last updated 2026-11-20):
Affected:
- Go package github.com/eclipse-keypont/crypto11/v2: through 2.0.0-rc8
- Go package github.com/eclipse-keypont/crypto11: through 1.6.8
- Go package github.com/ThalesGroup/crypto11: through 1.7.0-rc1
- Go package github.com/ThalesIgnite/crypto11: through 1.2.5
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-115407 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-115407 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/eclipse-keypont/crypto11/security/advisories/GHSA-c2cp-4qw8-q4jg
- https://github.com/eclipse-keypont/crypto11/commit/8d99b73c721c173ad85c0ca4e063c3da360a611d
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/491
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-115407
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-115407"}.

Affected versions

cve.now Index

36Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach10/20Affects Go packages
  • Severity9.1/10CVSS 9.1
  • No patch0/5No signal

What would change the score

  • Would score about 81 if added to CISA KEV
  • Would score about 76 if CISA's SSVC rates exploitation active
  • Would score about 41 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now

Evidence 5

KindSource
Vendor advisory 2Establishes: Affected and fixed versions.
AdvisoryGitHub · eclipse-keypont/crypto11 · Advisory GHSA-c2cp-4qw8-q4jg
Linkgitlab.eclipse.org · security/cve-assignment/-/work_items/491
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-115407
RecordNVD · CVE-2026-115407
Other links 1
PatchGitHub · eclipse-keypont/crypto11 · Commit 8d99b73c

Questions about CVE-2026-115407

Is CVE-2026-115407 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-115407?

github.com/eclipse-keypont/crypto11/v2 (Go): through 2.0.0-rc8. github.com/eclipse-keypont/crypto11 (Go): through 1.6.8. github.com/ThalesGroup/crypto11 (Go): through 1.7.0-rc1. github.com/ThalesIgnite/crypto11 (Go): through 1.2.5.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.