Improper Verification of Cryptographic Signature Affecting dotstatsuite-supercore package, versions <3.1.0_git20261022-r6


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.2% (11th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-DOTSTATSUITESUPERCORE-22505264
  • published12 Nov 2026
  • disclosed10 Nov 2026

Introduced: 10 Nov 2026

NewCVE-2026-125335  (opens in a new tab)
CWE-347  (opens in a new tab)

How to fix?

Upgrade Chainguard dotstatsuite-supercore to version 3.1.0_git20261022-r6 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream dotstatsuite-supercore package and not the dotstatsuite-supercore package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.3, ed25519.verify() decodes a public key in crypto_sign_open() without rejecting small-order points or their non-canonical encodings. With S = 0 and a small-order R value, an attacker who can choose the public key can produce signatures that verify for many messages, or all messages with the identity key, without a private key. This can defeat proof-of-possession, attribution, non-repudiation, or deduplication checks that rely on a signature being bound to the message. Keys produced by normal Ed25519 key generation are not small-order, so applications that verify only trusted or internally generated public keys are not affected. This issue is fixed in version 1.4.3.

CVSS Base Scores

version 3.1