CVE-2022-48195: An issue was discovered in Mellium mellium.im/sasl before 0.3.1

This month

CRITICAL 9.8REMOTEDOWNGRADE

CVE-2022-48195 is a critical-severity flaw (CVSS 9.8) affecting sasl. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 randomness being used during authentication.

Why this priority

Critical severity
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.9% (top 41%)
CISA exploited list	No
Weakness	CWE-287
Published	2022-12-31
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: mellium

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-12-31 01:15 UTCPublished CVE record published
2026-06-17 05:14 UTCUpdated Record last modified

mellium sasl DOWNGRADE

Affected: 0.3.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.3.0

1. Check installed version

apt-cache policy sasl || rpm -q sasl || sasl --version

2. No fixed release: DOWNGRADE to a release before 0.3.0 (Debian / Ubuntu)

apt-cache madison sasl sudo apt install sasl=<VERSION_BEFORE_0.3.0> sudo apt-mark hold sasl

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list sasl sudo dnf downgrade sasl-<VERSION_BEFORE_0.3.0> sudo dnf versionlock add sasl

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-48195?

sasl: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2022-48195 being exploited?

CVE-2022-48195 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-48195 affect?

CVE-2022-48195 affects sasl. Severity is critical (CVSS 9.8). 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 cau

How urgent is CVE-2022-48195?

Priority 54/100. Critical severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2026-56968 LOW 3.7 UPGRADE MITIGATE GNU SASL before 2.2.4 lacks sanitization of a short challenge in _gsasl_ntlm_client_step in the NTLM client, w

References

← Back to latest CVEs