CVE-2025-49140

Workarounds

At the application layer, reject any RTP packet where:

hasPadding (P-bit field) == true  &&  (padLen == 0 || padLen > packetLen, headerLen)

before passing it to Pion’s packet factories.

References

Commit fixing the bug: https://github.com/pion/interceptor/commit/fa5b35ea867389cec33a9c82fffbd459ca8958e5
Pull request: https://github.com/pion/interceptor/pull/338
Issue: https://github.com/pion/webrtc/issues/3148

Pion Interceptor versions v0.1.36 through v0.1.38 contain a bug in a RTP packet factory that can be exploited to trigger a panic with Pion based SFU via crafted RTP packets, This only affect users that use pion/interceptor.

The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap. Typical impact: resource exhaustion leading to denial of service.

CVE-2025-49140 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.1.39); upgrading removes the vulnerable code path.

Kodem intelligence

Upgrade to v0.1.39 or later, which includes PR #338 which validates that: padLen > 0 && padLen <= payloadLength and return error on overflow, avoiding panic.

If upgrading is not possible, apply the patch from the pull request manually or drop packets whose P-bit is set but whose padLen is zero or larger than the remaining payload.

1. What is CVE-2025-49140? CVE-2025-49140 is a high-severity allocation of resources without limits or throttling vulnerability in github.com/pion/interceptor (go), affecting versions >= 0.1.36, < 0.1.39. It is fixed in 0.1.39. The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap.
2. How severe is CVE-2025-49140? CVE-2025-49140 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/pion/interceptor are affected by CVE-2025-49140? github.com/pion/interceptor (go) versions >= 0.1.36, < 0.1.39 is affected.
4. Is there a fix for CVE-2025-49140? Yes. CVE-2025-49140 is fixed in 0.1.39. Upgrade to this version or later.
5. Is CVE-2025-49140 exploitable, and should I be worried? Whether CVE-2025-49140 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-49140 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-49140? Upgrade github.com/pion/interceptor to 0.1.39 or later.