Quick answers
- Is CVE-2026-34235 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-34235 being exploited in the wild.
- How severe is CVE-2026-34235?
- Critical severity, with a CVSS score of 9.1, published 31 March 2026.
- Which products and versions are affected?
- Teluu Pjsip < 2.17.
- Is there a fix for CVE-2026-34235?
- A patch was published on 2026-03-31: Fix committed to master branch (f4c7d08) and released in version 2.17 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-34235 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-34235?
- Check whether you run Teluu Pjsip at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A heap out-of-bounds read vulnerability (CWE-125) exists in PJSIP's VP9 RTP unpacketizer within the pjmedia-codec component. The root cause is insufficient bounds checking on the payload descriptor length when parsing VP9 Scalability Structure (SS) data. Specifically, the code fails to verify if the incremented descriptor length exceeds the actual RTP payload buffer size. A remote, unauthenticated attacker can exploit this by sending a crafted VP9 RTP stream to an application with video support enabled. This can result in information disclosure or a denial-of-service (DoS) condition. The vulnerability is addressed in version 2.17 by adding explicit bounds checks during SS parsing.
Affected products
- Teluu PJSIP < 2.17
Timeline
- 2026-03-30: advisory: GitHub Security Advisory GHSA-pqrm-53pc-wx28 published
- 2026-03-31: disclosed: CVE-2026-34235 published to NVD
- 2026-03-31: patched: Fix committed to master branch (f4c7d08) and released in version 2.17