dbcve.org
Pexip InfinityApplication · Pexip

CVE-2025-32096

HIGH · 7.5 CVSS v3.1 Published 2025-12-25
Fix available
A fix is available. Upgrade to 37.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Pexip Infinity 33.0 through 37.0 before 37.1 has improper input validation in signaling that allows an attacker to trigger a software abort, 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 confidence

Improper input validation in the signaling component of Pexip Infinity versions 33.0-37.0 allows unauthenticated remote attackers to send malformed signaling messages that trigger a software abort, causing denial of service. The vulnerability is network-exploitable and requires no authentication.

MitigationUpgrade Pexip Infinity to version 37.1 or later to obtain the vendor patch that implements proper input validation in the signaling pathway.

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
Pexip InfinityApplication
Affected:>= 33.0, < 37.1

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Pexip Infinity version
    Access the Pexip Infinity admin interface or use the command-line interface to retrieve the installed software version. This is typically visible in the system dashboard or via 'version' commands in the CLI.
    Affected if The installed version is 33.0, 33.1, 33.2, 33.3, 34.0, 34.1, 34.2, 34.3, 35.0, 35.1, 35.2, 35.3, 36.0, 36.1, 36.2, 36.3, 37.0, or any version greater than or equal to 33.0 but less than 37.1.
  2. Confirm signaling component is active
    Verify that the Pexip Infinity signaling service is running and accessible. The signaling component is a core part of the platform that handles call setup and negotiation between participants.
    Affected if The signaling component is enabled and operational, which is the default state for any functional Pexip Infinity deployment.
  3. Check network exposure of signaling port
    Identify the network interfaces and ports on which the Pexip Infinity signaling service is listening. This is typically port 443 or configured HTTPS ports in the deployment.
    Affected if The signaling service is exposed to untrusted networks, allowing unauthenticated external attackers to reach the signaling pathway.

You are affected if your Pexip Infinity version is 33.0 through 37.0 (inclusive) and the signaling component is accessible on the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 37.1 or later
Fixed in 37.1
Interim mitigation

Upgrade Pexip Infinity to version 37.1 or later to obtain the vendor patch that implements proper input validation in the signaling pathway.

Recommended fix High confidence

37.1

  1. Back up the current Pexip Infinity configuration and database before initiating the upgrade
  2. Download the Pexip Infinity version 37.1 upgrade package from the official Pexip portal or download site
  3. Review the release notes for version 37.1 to understand any specific upgrade requirements or prerequisites
  4. Apply the upgrade to the Pexip Infinity management node following standard upgrade procedures
  5. After upgrade completion, verify that all services are running correctly and the signaling component is operational
  6. Confirm the version number displays as 37.1 in the admin interface

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pexip Infinity Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32096 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-32096 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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