# CVE-2026-33069: PJSIP has an Out-of-bounds Read in SIP multipart parsing

> An out-of-bounds heap read in PJSIP allows attackers to read adjacent memory when processing SIP multipart messages, potentially disclosing sensitive data.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Mar 2026
- **Updated:** 20 Mar 2026
- **Also known as:** ALPINE-CVE-2026-33069, DEBIAN-CVE-2026-33069, GHSA-x5pq-qrp4-fmrj, UBUNTU-CVE-2026-33069

## What is CVE-2026-33069?

CVE-2026-33069 is a medium-severity memory corruption vulnerability in pjsip pjproject, published on 20 Mar 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. Versions 2.16 and below have a cascading out-of-bounds heap read in pjsip_multipart_parse(). After boundary string matching, curptr is advanced past the delimiter without verifying it has not reached the buffer end. This allows 1-2 bytes of adjacent heap memory to be read. All applications that process incoming SIP messages with multipart bodies or SDP content are potentially affected. This issue is resolved in version 2.17.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Pjsip Pjsip.

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

Upgrade to a fixed version.

## Is CVE-2026-33069 being exploited?

There is no known exploitation of CVE-2026-33069 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-40892](https://insights.sbomify.com/CVE-2026-40892/): PJSIP: Stack buffer overflow in pjsip_auth_create_digest2() (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-33069 is a medium-severity memory corruption vulnerability in pjsip pjproject, published on 20 Mar 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-33069 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-33069/ (Markdown: https://insights.sbomify.com/CVE-2026-33069/index.md)
```

## Sources

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

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