# CVE-2026-40614: PJSIP: Heap buffer overflow in Opus codec decoding

> A heap buffer overflow in PJSIP's Opus codec allows attackers to execute arbitrary code or cause denial of service via crafted audio frames.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 21 Apr 2026
- **Updated:** 22 Apr 2026
- **Also known as:** ALPINE-CVE-2026-40614, DEBIAN-CVE-2026-40614, GHSA-j59p-4xrr-fp8g, UBUNTU-CVE-2026-40614

## What is CVE-2026-40614?

CVE-2026-40614 is a high-severity memory corruption vulnerability in pjsip pjproject, published on 21 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

PJSIP is a free and open source multimedia communication library written in C. In 2.16 and earlier, there is a buffer overflow when decoding Opus audio frames due to insufficient buffer size validation in the Opus codec decode path. The FEC decode buffers (dec_frame[].buf) were allocated based on a PCM-derived formula: (sample_rate/1000) * 60 * channel_cnt * 2. At 8 kHz mono this yields only 960 bytes, but codec_parse() can output encoded frames up to MAX_ENCODED_PACKET_SIZE (1280) bytes via opus_repacketizer_out_range(). The three pj_memcpy() calls in codec_decode() copied input->size bytes without bounds checking, causing a heap buffer overflow.

Weakness: CWE-122 (Heap-based Buffer Overflow)

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

It affects 1 product.


Products: Pjsip Pjsip.

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

Upgrade to a fixed version.

## Is CVE-2026-40614 being exploited?

There is no known exploitation of CVE-2026-40614 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-32945](https://insights.sbomify.com/CVE-2026-32945/): PJSIP is vulnerable to Heap-based Buffer Overflow through DNS parser (high 8.4)
- [CVE-2026-40892](https://insights.sbomify.com/CVE-2026-40892/): PJSIP: Stack buffer overflow in pjsip_auth_create_digest2() (high 8.1)
- [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-40614 and fix it if it is affected.

What it is: CVE-2026-40614 is a high-severity memory corruption vulnerability in pjsip pjproject, published on 21 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-40614 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-40614/ (Markdown: https://insights.sbomify.com/CVE-2026-40614/index.md)
```

## Sources

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

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