# CVE-2025-53399: Security feature bypass in rtpengine

> Remote attackers can inject or intercept RTP/SRTP media streams due to origin-validation errors in Sipwise rtpengine's endpoint-learning logic.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:L/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Aug 2025
- **Updated:** 21 Jul 2026
- **Also known as:** DEBIAN-CVE-2025-53399, GHSA-9m93-62q8-9jmx, UBUNTU-CVE-2025-53399

## What is CVE-2025-53399?

CVE-2025-53399 is a medium-severity vulnerability in Sipwise rtpengine, published on 1 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Sipwise rtpengine before 13.4.1.1, an origin-validation error in the endpoint-learning logic of the media-relay core allows remote attackers to inject or intercept RTP/SRTP media streams via RTP packets (except when the relay is configured for strict source and learning disabled). Version 13.4.1.1 fixes the heuristic mode by limiting exposure to the first five packets, and introduces a recrypt flag that fully prevents SRTP attacks when both mitigations are enabled.

Weakness: CWE-346 (Origin Validation Error)

## Which versions are affected by CVE-2025-53399?


## How do I fix CVE-2025-53399?

Upgrade to a fixed version.

## Is CVE-2025-53399 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-53399 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-53399 and fix it if it is affected.

What it is: CVE-2025-53399 is a medium-severity vulnerability in Sipwise rtpengine, published on 1 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-53399 exists.

Affected product: Sipwise rtpengine. 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-2025-53399/ (Markdown: https://insights.sbomify.com/CVE-2025-53399/index.md)
```

## Sources

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

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