# CVE-2026-48829: Null dereference in GNU SASL

> A NULL pointer dereference in GNU SASL allows attackers to cause a denial of service via crafted DIGEST-MD5 tokens.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 May 2026
- **Updated:** 5 Jun 2026
- **Also known as:** DEBIAN-CVE-2026-48829, GHSA-5px8-3qcf-qpm5, SUSE-SU-2026:22313-1, UBUNTU-CVE-2026-48829, USN-8356-1, openSUSE-SU-2026:10891-1, openSUSE-SU-2026:21004-1

## What is CVE-2026-48829?

CVE-2026-48829 is a high-severity vulnerability in GNU SASL, published on 24 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In GNU SASL before 2.2.3, DIGEST-MD5 has a NULL pointer dereference affecting both clients and servers, via a known token with no accompanying = character. This occurs in lib/digest-md5/getsubopt.c.

Weakness: CWE-476 (NULL Pointer Dereference)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gsasl` | SUSE:Linux Enterprise Server 16.0 | All versions | 2.2.1-160000.3.1 |
| `gsasl` | SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 2.2.1-160000.3.1 |
| `gsasl` | openSUSE:Leap 16.0 | All versions | 2.2.1-160000.3.1 |
| `gsasl` | openSUSE:Tumbleweed | All versions | 2.2.3-1.1 |

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

Upgrade to a fixed version.

## Is CVE-2026-48829 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-48829 is a high-severity vulnerability in GNU SASL, published on 24 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-48829 in the wild and no public exploit code.

Affected product: GNU 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-48829/ (Markdown: https://insights.sbomify.com/CVE-2026-48829/index.md)
```

## Sources

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

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