# CVE-2026-40892: PJSIP: Stack buffer overflow in pjsip_auth_create_digest2()

> A stack buffer overflow in PJSIP allows attackers to execute arbitrary code or cause denial of service when using pre-computed digest credentials.

- **Severity:** High 8.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Apr 2026
- **Updated:** 21 Apr 2026
- **Also known as:** ALPINE-CVE-2026-40892, DEBIAN-CVE-2026-40892, GHSA-2wcg-w3c4-48r7, UBUNTU-CVE-2026-40892

## What is CVE-2026-40892?

CVE-2026-40892 is a high-severity memory corruption vulnerability in pjsip pjproject, published on 21 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PJSIP is a free and open source multimedia communication library written in C. In 2.16 and earlier, a stack buffer overflow exists in pjsip_auth_create_digest2() in PJSIP when using pre-computed digest credentials (PJSIP_CRED_DATA_DIGEST). The function copies credential data using cred_info->data.slen as the length without an upper-bound check, which can overflow the fixed-size ha1 stack buffer (128 bytes) if data.slen exceeds the expected digest string length.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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

It affects 1 product.


Products: Pjsip Pjsip.

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

Upgrade to a fixed version.

## Is CVE-2026-40892 being exploited?

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

## Other vulnerabilities in pjsip pjproject

- [CVE-2026-28799](https://insights.sbomify.com/CVE-2026-28799/): PJSIP: Heap use-after-free in PJSIP presence subscription termination handler (high 8.7)
- [CVE-2026-29068](https://insights.sbomify.com/CVE-2026-29068/): PJSIP: Stack buffer overflow in Opus codec parser (high 8.7)
- [CVE-2026-40614](https://insights.sbomify.com/CVE-2026-40614/): PJSIP: Heap buffer overflow in Opus codec decoding (high 8.5)
- [CVE-2026-32945](https://insights.sbomify.com/CVE-2026-32945/): PJSIP is vulnerable to Heap-based Buffer Overflow through DNS parser (high 8.4)
- [CVE-2026-26967](https://insights.sbomify.com/CVE-2026-26967/): PJSIP has a Heap-based Buffer Overflow vulnerability in its H.264 unpacketizer (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-40892 is a high-severity memory corruption vulnerability in pjsip pjproject, published on 21 Apr 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-40892 in the wild and no public exploit code.

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

## Sources

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

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