The Daily Byte
Breaking
Welcome to The Daily Byte — real stories from across Pakistan.
Saturday, 21 November 2026 · Pakistan

The Daily Byte

Stories from Pakistan that deserve to be heard

CVE-2026-129483: Cyrus SASL Login Bypass Flaw

By The Daily Byte ·16 Nov 2026 ·3 min read
Server room corridor with rows of racks in a data centre

A critical authentication flaw in Cyrus SASL could let an attacker log in as any user without knowing the password. The vulnerability, tracked as CVE-2026-129483, was published on 15 November 2026 and carries a CVSS score of 9.3, putting it in the critical range.

Cyrus SASL is the authentication library used by mail servers and other network services to check usernames and passwords. The flaw sits in its Secure Remote Password (SRP) mechanism, the part of the software that is supposed to prove a user's identity without sending the password itself across the network.

How the bypass works

According to the vulnerability record, the SRP server code in the file plugins/srp.c does not reject client public values, known as A, that are multiples of N, a large number used in the SRP maths. An unauthenticated attacker on the network can send a value of A equal to N, which forces the shared secret between client and server to zero.

Once the shared secret is zero, the attacker can authenticate as any existing user without the password, and can also learn the session keys for the connection. The flaw is classed as CWE-287, improper authentication, and it affects Cyrus SASL through version 2.1.28. No fixed version is listed in the CVE record, so administrators should check the vendor's advisory and the project's own repository, where a fix commit has been published.

Who is affected

Any service that uses Cyrus SASL with the SRP mechanism switched on is exposed. That typically means mail servers and other systems that rely on the library for login checks, and the attack can be carried out remotely by anyone who can reach the service on the network. No user interaction is needed and no account of the attacker's own is required.

There is no confirmed evidence of the flaw being exploited in the wild, and it has not been added to the US Cybersecurity and Infrastructure Security Agency's Known Exploited Vulnerabilities catalogue. That is no reason to delay, however: authentication bypasses of this severity tend to attract attention quickly once the details are public, and the disclosure itself explains exactly how to trigger the flaw.

What to do now

Administrators should apply the latest update from the vendor as soon as it is available for their system. Until a patched version can be installed, the safest step is to disable the SRP authentication mechanism. Teams should also check which of their services use Cyrus SASL at all, since the library is often pulled in as a dependency of mail software and may be running on systems nobody thinks of as authentication servers.

Internet-facing systems should be treated as the priority, followed by internal services that accept logins from across the network. After patching, it is worth reviewing authentication logs for unusual logins, because an attacker who used the flaw would appear as a legitimate user. Full details are in the vulnerability record at ThreatRoundup.