On this page (7 sections)

A critical authentication bypass, tracked as CVE-2026-129483, affects the SRP server mechanism in Cyrus SASL through version 2.1.28. According to the GitHub advisory and the NVD record, an unauthenticated network client can authenticate as any existing user without knowing the password.

If you run mail, directory or other network services that use Cyrus SASL, especially with the SRP mechanism enabled, you should check your exposure now. The advisory does not list affected or patched versions in a structured way, so this article focuses on what is confirmed and how to reduce risk while details settle.

What happened

The vulnerability was published on November 15, 2026. The description says the function srp_server_mech_step2 in the SRP server mechanism does not reject client public values (called A) that are multiples of N. A network client with no credentials can send A equal to N, which forces a zero shared secret. The result, per the advisory, is authentication as any existing user without the password, and the attacker also learns session keys.

The GitHub entry is marked unreviewed and lists no package, and the NVD text simply repeats it, so these are effectively one source rather than two confirmations. The advisory lists several references: an upstream issue, a commit, a post on seclists.org, a VulnCheck page and a gist. The contents of those pages were not included in our research and we have not reviewed them, so we do not describe what they say.

Technical details

From the advisory: the SRP server code in srp_server_mech_step2 does not reject client public values A that are multiples of N. Sending A equal to N forces a zero shared secret, which lets an unauthenticated client authenticate as any existing user and learn session keys. The weakness is classed as CWE-287 (improper authentication).

The CVSS v4 metrics on the advisory describe it as network-reachable, low complexity, needing no privileges and no user interaction, with high confidentiality and integrity impact on the vulnerable system and no availability impact.

General background, not taken from the research: SRP (Secure Remote Password) is designed so a client can prove it knows a password without sending it, and both sides derive a shared secret used for session keys. Servers using it are expected to refuse invalid public values from the client. Here, the advisory says the Cyrus SASL server does not.

The advisory says the bypass lets the attacker authenticate as an existing user. The research does not describe what data an attacker could reach after logging in, because that depends on the application using Cyrus SASL.

Who is affected

Cyrus SASL is a library used by other software to handle authentication. Realistic exposure depends on three things:

  • You run a version of Cyrus SASL up to and including 2.1.28.
  • The SRP mechanism is actually available to clients on a network-facing service. The advisory describes a flaw in the SRP server mechanism only, so services that do not offer SRP are not described as affected, though you should confirm this for your setup.
  • The service is reachable by untrusted clients, for example over the internet or a shared network.

Many deployments use other mechanisms and may never expose SRP. The research does not say which applications or distributions are affected, so do not assume either way until you check.

How to check your exposure

Start by finding which Cyrus SASL version is installed. These are read-only package queries.

Check the installed Cyrus SASL library version (Debian/Ubuntu)Shell
dpkg -l | grep -i sasl
Check the installed Cyrus SASL library version (RHEL, Rocky, Alma, Fedora)Shell
rpm -qa | grep -i cyrus-sasl

Next, see whether an SRP plugin is present on the system. This lists files with srp in the name under common library directories and only reads the file system; no output generally means the plugin is not installed in those locations.

Look for an installed SRP plugin for SASL (any Linux)Shell
find /usr/lib /usr/lib64 /usr/local/lib -iname '*srp*' 2>/dev/null | grep -i sasl

Then review the SASL configuration of the services that use it (for example the mechanism list in the application's SASL settings) and check whether SRP is listed as an allowed mechanism. Config file names and locations differ per application, so consult that application's documentation.

What to do now

  1. Inventory every server that uses Cyrus SASL and record the installed version.
  2. Watch the upstream issue and your distribution's security tracker for a fixed release; the advisory does not name one.
  3. Note that the advisory lists a commit among its references. The research does not say whether it is the fix, so ask your vendor or maintainer before relying on it.
  4. Where SRP is not needed, remove it from the list of enabled mechanisms for network-facing services.
  5. Restrict access to affected services with firewall rules or VPN so only trusted networks can reach them.
  6. Apply distribution updates for Cyrus SASL as soon as a fix is published, then restart the dependent services.
  7. After remediation, review authentication logs for suspicious logins and rotate credentials and sessions for sensitive accounts if you see any.

To see whether your distribution already offers a Cyrus SASL update, run the matching read-only query below and look for sasl packages in the output.

Check for available Cyrus SASL package updates (Debian/Ubuntu)Shell
sudo apt update && apt list --upgradable 2>/dev/null | grep -i sasl
Check for available Cyrus SASL package updates (RHEL, Rocky, Alma, Fedora)Shell
dnf check-update | grep -i cyrus-sasl
Caution. Restarting mail, directory or authentication services interrupts logins for connected users. Schedule the restart in a maintenance window and confirm the service starts cleanly afterwards.
Tip. If you cannot patch yet, limiting who can reach the service and disabling SRP are the most direct mitigations suggested by the nature of the flaw. Neither is confirmed by the vendor in the research, so treat them as risk reduction, not a cure.

Detection and monitoring

The advisory does not describe log signatures for this attack, so we cannot give a reliable detection pattern. Practical steps are to look for successful logins from unfamiliar addresses, successful authentication events for accounts that are normally idle, and logins that do not match a user's usual locations or times. Compare these with your service's own authentication logs.

The advisory states that the attacker also learns session keys. The research does not describe what data that could expose, so if you find a suspicious SRP login, treat the account as compromised and review what it could access.

For the public side of your infrastructure, an outside-in view helps you confirm which services are reachable at all. Webforta Scan runs read-only scans of sites you verify, and Webforta Monitor can alert on certificate and DNS changes. Neither tells you whether a given library version on your server is vulnerable, so keep the version inventory above.

What we do not know yet

  • No fixed Cyrus SASL version is named in the advisory, and affected versions are marked unknown beyond the phrase through 2.1.28.
  • The GitHub entry is unreviewed, and only one independent publisher covers the story so far.
  • There is no report of exploitation in the research, and the CVE is not listed in CISA's KEV catalog.
  • Which downstream products and distributions ship an affected SRP plugin is not stated.
  • Whether the commit listed in the references is the fix is not stated.

Treat these as open until the upstream project or your distribution confirms them. For more background on securing servers and websites, see our small business website security guide.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-129483 - GitHub Advisory Databasegithub.com
  2. CVE-2026-129483: Cyrus SASL through 2.1.28 contains an authentication bypass vulnerability in the SRP server mechanism because srp_server_mech_step2 does not reject client…nvd.nist.gov ·
  • Cyrus SASL
  • CVE-2026-129483
  • authentication bypass
  • SRP
  • mail servers