In limbo for 20 days
GHSA-c2cp-4qw8-q4jg
github.com/eclipse-keypont/crypto11/v2 on Go · published in eclipse-keypont/crypto11
Facts
- Severity
- High · CVSS score 7.4CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
- Affected versions (github.com/eclipse-keypont/crypto11/v2)
- <= 2.0.0-rc8As entered by the maintainer. Not reviewed.
- Fixed in (github.com/eclipse-keypont/crypto11/v2)
- 2.0.0-rc9
- Affected versions (github.com/eclipse-keypont/crypto11)
- <= 1.6.8As entered by the maintainer. Not reviewed.
- Fixed in (github.com/eclipse-keypont/crypto11)
- not stated
- Affected versions (github.com/ThalesGroup/crypto11)
- <= 1.7.0-rc1As entered by the maintainer. Not reviewed.
- Fixed in (github.com/ThalesGroup/crypto11)
- not stated
- Affected versions (github.com/ThalesIgnite/crypto11)
- <= 1.2.5As entered by the maintainer. Not reviewed.
- Fixed in (github.com/ThalesIgnite/crypto11)
- not stated
- CVE
- None cited by the advisory
- GitHub Advisory Database
- Not reviewed
- OSV.dev
- Not present
- Other CVEs pointing here
- None found in the CVE List
If you use github.com/eclipse-keypont/crypto11/v2 <= 2.0.0-rc8
Upgrade to 2.0.0-rc9 or later. Dependabot, npm audit and OSV-Scanner won’t flag this yet.
Timeline
2026-10-22 16:38 UTC
Published by the maintainers
No CVE cited
2026-10-28 09:42 UTC
First seen by Limbowatch
not reviewed · not in OSV
Waiting
Reviewed by GitHub
Waiting
In OSV; scanners can see it
Machine-readable record: feed/GHSA-c2cp-4qw8-q4jg.json