Is CVE-2026-89316 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-89316 being exploited in the wild.

How severe is CVE-2026-89316?

Informational severity, published 23 October 2026.

Which products and versions are affected?

Eclipse Keypoint Gose before 1.0.0-rc4; Thales Group Gose 0.7.3 to 0.13.0-rc1.

How is CVE-2026-89316 attacked?

It is attacked over the network.

Am I affected by CVE-2026-89316?

Check whether you run Eclipse Keypoint Gose or Thales Group Gose at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-89316: gose LoadPublicKey panic on kty/alg mismatch

CVE-2026-89316 · Severity: info · Published 2026-10-23

gose is a cryptographic library that processes JSON Web Keys (JWK) for digital signature verification. When LoadPublicKey processes a JWK with mismatched key type and algorithm (e.g., an EC key marked with an RSA algorithm), the library panics rather than returning an error, causing a denial of service. Applications that directly parse external JWK documents are at risk of crashes.

Quick answers

Is CVE-2026-89316 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-89316 being exploited in the wild.
How severe is CVE-2026-89316?: Informational severity, published 23 October 2026.
Which products and versions are affected?: Eclipse Keypoint Gose before 1.0.0-rc4; Thales Group Gose 0.7.3 to 0.13.0-rc1.
Is there a fix for CVE-2026-89316?: Yes: fixed in eclipse-keypont/gose 1.0.0-rc4 or later; Thales Group users must migrate to eclipse-keypont/gose. Until then: Do not pass externally supplied JWK documents directly to LoadPublicKey or LoadPrivateKey. Use NewVerificationKey instead, or validate that kty and alg match before loading (EC keys must carry ES256, ES384, or ES512). Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-89316 attacked?: It is attacked over the network.
Am I affected by CVE-2026-89316?: Check whether you run Eclipse Keypoint Gose or Thales Group Gose at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: eclipse-keypont/gose 1.0.0-rc4 or later; Thales Group users must migrate to eclipse-keypont/gose

Do not pass externally supplied JWK documents directly to LoadPublicKey or LoadPrivateKey. Use NewVerificationKey instead, or validate that kty and alg match before loading (EC keys must carry ES256, ES384, or ES512).

Technical details

LoadPublicKey performs an unchecked type assertion `algToOptsMap[alg].(*ECDSAOptions)` when processing EC keys, which panics if the algorithm does not map to ECDSAOptions. A JWK declaring `"kty":"EC"` with a non-EC `"alg"` (permitted by RFC 7517) triggers this panic. The vulnerability requires an application to pass external JWK bytes directly to LoadPublicKey; internal library code paths like NewVerificationKey perform proper validation and are not affected.

Affected products

Thales Group gose 0.7.3 to 0.13.0-rc1
Eclipse Keypoint gose before 1.0.0-rc4

Timeline

2026-09-01: disclosed: GHSA-fv39-8484-f4wr published
2026-10-23: advisory: CVE-2026-89316 published on NVD

References

https://github.com/eclipse-keypont/gose/security/advisories/GHSA-fv39-8484-f4wr

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.