Improper Input Validation 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.43% (39th 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-22504875
  • published12 Nov 2026
  • disclosed10 Nov 2026

Introduced: 10 Nov 2026

NewCVE-2026-125332  (opens in a new tab)
CWE-20  (opens in a new tab)
CWE-248  (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, a forge.tls client accepts a ServerHello compression_method that it did not offer. When the client later handles ServerHelloDone, tls.createConnectionState() rejects the unsupported compression algorithm by throwing an Error that propagates from connection.process(). A malicious server or an on-path attacker can alter the unauthenticated ServerHello compression byte before the server Finished message and terminate a Node.js process when the application does not catch the exception. The affected client paths include direct forge.tls use, forge.tls.wrapSocket, and forge.http; forge.tls servers are not affected, and the issue has no confidentiality or integrity impact. This issue is fixed in version 1.4.3.

CVSS Base Scores

version 3.1