CVE-2025-65102: PJSIP is vulnerable to buffer overflow in Opus PLC

Published Nov 21, 2025
·
Updated

PJSIP is a free and open source multimedia communication library. Prior to version 2.16, Opus PLC may zero-fill the input frame as long as the decoder ptime, while the input frame length, which is based on stream ptime, may be less than that. This issue affects PJSIP users who use the Opus audio codec in receiving direction. The vulnerability can lead to unexpected application termination due to a memory overwrite. This issue has been patched in version 2.16.

Affected Software

1 affected component
PJSIP PJSIP<2.16

Event History

Nov 21, 2025
CVE Published
via MITRE·09:36 PM
Data Sourced
via MITRE·09:36 PM
DescriptionWeakness
Data Sourced
via NVD·10:16 PM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-65102?

CVE-2025-65102 is considered a moderate severity vulnerability affecting PJSIP before version 2.16.

2

How do I fix CVE-2025-65102?

To fix CVE-2025-65102, upgrade PJSIP to version 2.16 or later.

3

Who is affected by CVE-2025-65102?

CVE-2025-65102 affects users of PJSIP versions prior to 2.16 that utilize Opus PLC.

4

What is the impact of CVE-2025-65102?

The impact of CVE-2025-65102 is that it may lead to improper handling of input frames by the Opus PLC decoder.

5

Is there a workaround for CVE-2025-65102?

There are no official workarounds for CVE-2025-65102 other than upgrading to the patched version.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203