CVE-2026-129483

CRITICALPre-NVD 9.19.1
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-11-15. A secondary CVSS source baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-126032 (ENISA EUVD) · GHSA-h9fw-9v74-m2cr (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
9.1
EG Score
9.1CRITICALhigh confidence
EG Risk
72
EG Risk 72/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
33rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 15, 2026

Last Modified

November 18, 2026

Advisory Details (6)

Auto-updated Nov 15, 2026
Patch available. Sources: github_commit.
Web page

Cyrus SASL through 2.1.28 SRP Authentication Bypass via plugins/srp.c | Advisories | VulnCheck

https://www.vulncheck.com/advisories/cyrus-sasl-through-2.1.28-srp-authentication-bypass-via-plugins-srp-c
Web page

cyrus-sasl/plugins/srp.c at cyrus-sasl-2.1.28 · cyrusimap/cyrus-sasl · GitHub

https://github.com/cyrusimap/cyrus-sasl/blob/cyrus-sasl-2.1.28/plugins/srp.c#L2046-L2050
GitHub commit

commit fb3724f43dc5 (cyrusimap/cyrus-sasl)

Fix landed in cyrusimap/cyrus-sasl commit fb3724f43dc5 — awaiting tagged release

https://github.com/cyrusimap/cyrus-sasl/commit/fb3724f43dc50247ff2bf02135457d6d77031654
Web page

cyrus-sasl SRP auth bypass (A == 0 mod N) — E2E reproducer for issue #896 · GitHub

https://gist.github.com/afldl/18d15d3f5a1df99411e35000c7de80db
Web page

oss-sec: Unfixed vulnerabilities in Cyrus SASL

https://seclists.org/oss-sec/2026/q4/122
Web page

[Security] SRP server authentication bypass: A == 0 (mod N) not rejected (CWE-347) · Issue #896 · cyrusimap/cyrus-sasl · GitHub

https://github.com/cyrusimap/cyrus-sasl/issues/896

Vendor Advisories for CVE-2026-129483(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 19× in last 7d / 21× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 20:33 UTCEchelonGraph re-scored
  2. 2026-11-21 20:33 UTCGHSA enrichmentGHSA-h9fw-9v74-m2cr · GitHub severity CRITICAL · GitHub CVSS 9.1
  3. 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  4. 2026-11-20 21:54 UTCEchelonGraph re-scored
  5. 2026-11-20 21:54 UTCVendor advisory
  6. 2026-11-20 21:54 UTCGHSA enrichmentGHSA-h9fw-9v74-m2cr · GitHub severity CRITICAL · GitHub CVSS 9.1
  7. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  8. 2026-11-19 23:16 UTCEchelonGraph re-scored
  9. 2026-11-19 23:16 UTCVendor advisory
  10. 2026-11-19 23:16 UTCGHSA enrichmentGHSA-h9fw-9v74-m2cr · GitHub severity CRITICAL · GitHub CVSS 9.1
  11. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  12. 2026-11-19 14:07 UTCEchelonGraph re-scored
  13. 2026-11-19 14:07 UTCGHSA enrichmentGHSA-h9fw-9v74-m2cr · GitHub severity CRITICAL · GitHub CVSS 9.1
  14. 2026-11-18 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  15. 2026-11-18 15:28 UTCEchelonGraph re-scored
  16. 2026-11-18 15:28 UTCGHSA enrichmentGHSA-h9fw-9v74-m2cr · GitHub severity CRITICAL · GitHub CVSS 9.1
  17. 2026-11-18 14:42 UTCEchelonGraph re-scored
  18. 2026-11-18 14:42 UTCGHSA enrichmentGHSA-h9fw-9v74-m2cr · GitHub severity CRITICAL · GitHub CVSS 9.1
  19. 2026-11-18 14:28 UTCEchelonGraph re-scored
  20. 2026-11-18 14:28 UTCGHSA enrichmentGHSA-h9fw-9v74-m2cr · GitHub severity CRITICAL · GitHub CVSS 9.1
  21. 2026-11-18 11:44 UTCEchelonGraph re-scored
  22. 2026-11-18 11:44 UTCGHSA enrichmentGHSA-h9fw-9v74-m2cr · GitHub severity CRITICAL · GitHub CVSS 9.1
  23. 2026-11-17 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  24. 2026-11-17 13:05 UTCEchelonGraph re-scored
  25. 2026-11-17 13:05 UTCGHSA enrichmentGHSA-h9fw-9v74-m2cr · GitHub severity CRITICAL · GitHub CVSS 9.1
Show 8 more
  1. 2026-11-16 16:49 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  2. 2026-11-16 14:25 UTCGHSA enrichmentGHSA-h9fw-9v74-m2cr · GitHub severity CRITICAL · GitHub CVSS 9.1
  3. 2026-11-15 15:46 UTCEchelonGraph re-scored
  4. 2026-11-15 15:46 UTCGHSA enrichmentGHSA-h9fw-9v74-m2cr · GitHub severity CRITICAL · GitHub CVSS 9.1
  5. 2026-11-15 14:29 UTCEchelonGraph re-scored
  6. 2026-11-15 14:02 UTCENISA EUVD ID recordedEUVD-2026-126032 · Source: ENISA EUVD
  7. 2026-11-15 13:50 UTCEchelonGraph re-scoredFirst assessed: 9.1 CRITICAL
  8. 2026-11-15 13:49 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-129483?
CVE-2026-129483 is a critical-severity vulnerability; its CVE record was published on November 15, 2026. 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…
When was CVE-2026-129483 made public?
CVE-2026-129483 was made public on July 31, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on November 15, 2026. EchelonGraph's copy of the record carries a last-modified date of November 18, 2026; the record at its source may have been updated since.
Is CVE-2026-129483 actively exploited?
CVE-2026-129483 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-129483?
CVE-2026-129483 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-129483?
A fix for CVE-2026-129483 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-129483 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-129483

Explore →

Is Your Infrastructure Affected by CVE-2026-129483?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.