CVE-2025-66379
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedPexip Infinity before 39.0 has Improper Input Validation in the media implementation, allowing a remote attacker to trigger a software abort via a crafted media stream, resulting in a denial of service.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencePexip Infinity versions before 39.0 contain an improper input validation vulnerability in the media implementation. A remote attacker can send a crafted malicious media stream to trigger a software abort, causing a denial of service condition.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 39.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Pexip Infinity versionAccess the Pexip Infinity admin interface or use the system management CLI to retrieve the installed software version. This is typically found in the admin dashboard under System > Overview or via command line tools provided by the platform.Affected if The installed version is any version before 39.0 (e.g., 38.x, 37.x, etc.)
-
Confirm media services are exposedVerify that the Pexip Infinity node is configured to accept incoming media streams from external sources. Check the media configuration settings in the admin interface to see which network interfaces and ports are enabled for media reception.Affected if Media services are enabled and the system accepts incoming media connections from untrusted networks or external participants.
-
Review network exposureExamine firewall rules and network configuration to determine if the media ports (typically UDP/TCP ports for SIP, H.323, or WebRTC media) are accessible from outside the trusted network.Affected if The media services are reachable from untrusted or public networks without adequate filtering.
You are affected if your Pexip Infinity version is below 39.0 and the system is configured to accept incoming media streams from external or untrusted sources.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped39.0
Upgrade Pexip Infinity to version 39.0 or later to remediate this vulnerability. Organizations should also consider network segmentation to limit exposure of the video conferencing infrastructure to untrusted networks.
Pexip Infinity 39.0 or later
- Consult the official Pexip upgrade documentation at docs.pexip.com for version 39.0
- Perform a full backup of the current Pexip Infinity configuration and database
- Download Pexip Infinity version 39.0 or later from the official Pexip distribution portal
- Execute the upgrade following the documented upgrade procedure specific to your deployment type
- Verify the upgrade was successful and confirm the media implementation is functioning correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-66379 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-66379 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data