# CVE-2026-132138: Cyrus-sasl: scram channel-binding null dereference allows remote denial of service


- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 18 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-132138, DHI-k4bq-jg3u-mze2-63vu, ECHO-4680-ee79-3611, GHSA-38vc-v59c-g6p7, UBUNTU-CVE-2026-132138

## What is CVE-2026-132138?

CVE-2026-132138 is a medium-severity vulnerability in cyrus-sasl, published on 18 Nov 2026. 

### Official description

A flaw was found in cyrus-sasl. When processing authentication requests using the Salted Challenge Response Authentication Mechanism (SCRAM), a remote attacker can trigger a null pointer dereference by submitting unexpected channel-binding data. This causes the server process to crash before validating authentication proofs, leading to a Denial of Service (DoS).

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2026-132138?

It affects 2 products.


Products: Red Hat Enterprise Linux, Redhat Rhel Els.

CPE match criteria (CPE 2.3):

- `cpe:2.3:a:redhat:enterprise_linux:10:*:*:*:*:*:*:*`
- `cpe:2.3:a:redhat:enterprise_linux:8:*:*:*:*:*:*:*`
- `cpe:2.3:a:redhat:enterprise_linux:9:*:*:*:*:*:*:*`
- `cpe:2.3:o:redhat:rhel_els:7:*:*:*:*:*:*:*`

## How do I fix CVE-2026-132138?

No fix has been published for CVE-2026-132138 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-132138 being exploited?

There is no known exploitation of CVE-2026-132138 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-132138 and fix it if it is affected.

What it is: CVE-2026-132138 is a medium-severity vulnerability in cyrus-sasl, published on 18 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-132138 in the wild and no public exploit code.

Affected product: cyrus-sasl. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-132138/ (Markdown: https://insights.sbomify.com/CVE-2026-132138/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-132138
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-132138
- OSV: https://osv.dev/vulnerability/CVE-2026-132138

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-132138/
Summaries are generated and may contain mistakes; the official description above is the record.
