go package report

Is mellium.im/sasl safe?

1 known vulnerability, worst severity CRITICAL.

cvss
9.8

how bad it is if exploited, out of 10

epss
0.90%

chance of exploitation in the next 30 days

xyz score
4.2

CyberXYZ composite, out of 10

fig. 01 — GHSA-gvfj-fxx3-j323, the advisory selected below

// advisories

GHSA-gvfj-fxx3-j323

CRITICALCVE-2022-48195

An issue was discovered in Mellium mellium.im/sasl before 0.3.1. When performing SCRAM-based SASL authentication, if the remote end advertises support for channel binding, no random nonce is generated (instead, the nonce is empty). This causes authentication to fail in the best case, but (if paired with a remote end that does not validate the length of the nonce) could lead to insufficient randomn

Affected
< 0.3.1
Fixed in
0.3.1
Weakness
CWE-287
Published
2022-12-31
Source
github

GHSANVDMITREreferencereferencereferencereference

// dependencies

0 direct

Sign in for dependency paths and remediation

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so go packages are not covered.

Checked 2026-09-22 at 00:50 UTC. The most recent advisory here was published 2022-12-31. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.
Is mellium.im/sasl safe? go package security report | CyberXYZ