Skip to main content
Menu
CVEs

CVE

Cyrus SASL authentication bypass in SRP mechanism

Only affects Cyrus SASL through 2.1.28 and current master when the SRP server mechanism is in use. No fixed version is listed.

CVE-2026-129483EUVD-2026-126032GHSA-H9FW-9V74-M2CR

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

9.3CriticalCNA
Exploited
No known exploitation
Fix
Fix or patch referenced
Who is exposed
Not reported

Do first: Apply the patch listed under Evidence.

Published
Last modified
Reference
Last checked
0.38% · 32nd percentile
26/100 · provisional
Unclear
None on Exploit-DB, Metasploit or GitHub
On X
View the cve.now post

Summary

Cyrus SASL, an authentication library, has an authentication bypass in its SRP mechanism that lets a remote, unauthenticated attacker log in as any existing user without the password and learn session keys. The flaw is in how the server handles client public values that are multiples of N, which it fails to reject.

Original description

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 public values A that are multiples of N. Unauthenticated network clients can send A equal to N to force a zero shared secret, authenticating as any existing user without the password and learning session keys.

Who should check

Teams running Cyrus SASL 2.1.28 or current master with the SRP server mechanism enabled, including cyrus-imapd deployments that use SASL SRP.

“The SRP server mechanism in cyrus-sasl 2.1.28 (and current master)”

github.com

cve.now Index

26Pcve.now Index 26 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.3/10CVSS 9.3
  • No patch0/5No signal

What would change the score

  • Would score about 71 if added to CISA KEV
  • Would score about 66 if CISA's SSVC rates exploitation active
  • Would score about 31 if advisories confirm default setups are exposed

What to do

  • Apply the patch listed under Evidence.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-129483 (Cyrus SASL through 2.1.28 SRP Authentication Bypass via plugins/srp.c), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129483 (entry last updated 2026-11-15):
Affected:
- cyrusimap cyrus-sasl: through 2.1.28
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Cyrus SASL 2.1.28 or current master with the SRP server mechanism (source: https://github.com/cyrusimap/cyrus-sasl/issues/896)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-129483 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129483 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/cyrusimap/cyrus-sasl/commit/fb3724f43dc50247ff2bf02135457d6d77031654
- https://github.com/cyrusimap/cyrus-sasl/issues/896
- https://seclists.org/oss-sec/2026/q4/122
- https://github.com/cyrusimap/cyrus-sasl/blob/cyrus-sasl-2.1.28/plugins/srp.c#L2046-L2050
- https://www.vulncheck.com/advisories/cyrus-sasl-through-2.1.28-srp-authentication-bypass-via-plugins-srp-c
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129483
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129483"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now

Affected versions

  • cyrusimap cyrus-sasl

    through 2.1.28

Evidence 8

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Public exploit code · 1

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

  1. Exploit

Write-ups · 1

Establishes: Technical detail and context.

  1. Link

Other links · 4

  1. Patch
  2. Report
  3. Repository
  4. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-129483

Is CVE-2026-129483 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

The SRP server mechanism in Cyrus SASL can be bypassed, letting an attacker authenticate as any existing user without the password and learn session keys.Source: github.com, vulncheck.com

Which versions are affected by CVE-2026-129483?

cyrus-sasl: through 2.1.28.Source: cve.now feed data

Am I affected, and how do I check?

Cyrus SASL versions up to and including 2.1.28, and current master, are affected when the SRP server mechanism is in use. To check, confirm the installed version and whether the server offers the SRP mechanism.Source: github.com, vulncheck.com

How do I fix CVE-2026-129483?

The checked facts list no fixed version and no vendor patch IDs, so no upgrade target can be named. Check the vendor's advisory for a fix and update when one is published.Source: github.com, vulncheck.com