Improper Certificate Validation Affecting sqlpad package, versions <7.5.7-r39


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.57% (45th 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-SQLPAD-19641790
  • published8 Sept 2026
  • disclosed28 Aug 2026

Introduced: 28 Aug 2026

CVE-2026-55215  (opens in a new tab)
CWE-295  (opens in a new tab)
CWE-522  (opens in a new tab)

How to fix?

Upgrade Chainguard sqlpad to version 7.5.7-r39 or higher.

NVD Description

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

MariaDB Connector/Node.js is used to connect applications developed on Node.js to MariaDB and MySQL databases. Prior to versions 3.3.3, 3.4.6, and 3.5.3, when ssl is enabled without a pinned CA or server certificate, MariaDB Connector/Node.js sends credentials before completing certificate fingerprint validation. In lib/cmd/handshake/auth/handshake.js, a server that selects mysql_clear_password as the initial authentication plugin can receive the password before the post-TLS identity check. In lib/cmd/handshake/authentication.js, an authentication switch can evaluate the previous plugin instead of the requested target plugin, allowing mysql_clear_password to send the credential first. An active man-in-the-middle can present a self-signed certificate, capture the database password, and use it to authenticate directly even though the connector later rejects the server and closes the connection. This issue is fixed in versions 3.3.3, 3.4.6, and 3.5.3.