CVE-2025-66443
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 35.0 through 38.1 before 39.0, in non-default configurations that use Direct Media for WebRTC, has Improper Input Validation in signalling that allows an attacker to trigger a software abort, resulting in a temporary 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 35.0 through 38.1 contain an improper input validation vulnerability in the signalling component when Direct Media for WebRTC is enabled (non-default configuration). Attackers can send specially crafted input to trigger a software abort, causing temporary denial of service.
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>= 35.0, < 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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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 installed Pexip Infinity versionAccess the Pexip Infinity admin interface or use the command-line management tool to retrieve the currently installed version number.Affected if The installed version is 35.0, 36.x, 37.x, 38.0, or 38.1 (versions below 39.0).
-
Locate Direct Media for WebRTC settingNavigate to the Pexip Infinity admin interface under the conferencing configuration or WebRTC settings section where Direct Media for WebRTC is configured.Affected if Unable to locate or the setting is not found in the expected configuration area.
-
Verify Direct Media for WebRTC statusExamine the configuration value for Direct Media for WebRTC to determine whether it is enabled or disabled.Affected if Direct Media for WebRTC is explicitly set to enabled.
You are affected if your Pexip Infinity version is 35.0 or higher but below 39.0 AND Direct Media for WebRTC is enabled in your configuration.
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 to Pexip Infinity version 39.0 or later to obtain the vendor patch. If upgrade is not immediately feasible, assess whether the non-default Direct Media for WebRTC configuration can be disabled.
39.0
- Review the Pexip Infinity upgrade documentation at docs.pexip.com for upgrade prerequisites and procedures
- Download Pexip Infinity version 39.0 from the official Pexip download portal
- Follow the standard upgrade procedure to apply version 39.0 to your Pexip Infinity deployment
- After upgrade, verify that the Direct Media for WebRTC functionality is working correctly
- Confirm the version upgrade was successful by checking the admin interface
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-66443 — 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-66443 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