dbcve.org
Pexip InfinityApplication · Pexip

CVE-2025-32095

HIGH · 7.5 CVSS v3.1 Published 2025-12-25
Fix available
A fix is available. Upgrade to 37.0 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 before 37.0 has improper input validation in signalling that allows a remote attacker to trigger a software abort via a crafted signalling message, 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 · moderate confidence

Pexip Infinity before version 37.0 contains improper input validation in its signalling component. A remote attacker can send a crafted signalling message that triggers a software abort, causing denial of service (DoS). The CVSS 7.5 score reflects high availability impact from this crash condition.

MitigationUpgrade Pexip Infinity to version 37.0 or later to address the input validation vulnerability. Prior to upgrade, assess current deployment version and verify upgrade compatibility in a staging environment.

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:< 37.0

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. Verify Pexip Infinity is installed
    Check for Pexip services or processes running on the system. Look for 'pexip' named processes or services in the system service list.
    Affected if Pexip Infinity services or processes are found on the host
  2. Determine the installed Pexip Infinity version
    Access the Pexip Infinity admin interface or use the command line management tool to retrieve the current software version. Navigate to System > Overview in the admin GUI or run the management CLI command to display version information.
    Affected if The displayed version number is lower than 37.0
  3. Confirm the signalling component is enabled
    Check the Pexip Infinity configuration to verify the signalling service is active and accessible. In the admin interface, review the Conferencing Nodes status and ensure the signalling service is running.
    Affected if The signalling component is enabled and accessible on the network
  4. Verify version against affected range
    Compare the identified version against the vulnerable range: any version below 37.0 is affected.
    Affected if The installed version is below 37.0 and the signalling component is exposed

The environment is affected if Pexip Infinity is installed with a version lower than 37.0 and the signalling component is enabled and accessible.

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.0 or later
Fixed in 37.0
Interim mitigation

Upgrade Pexip Infinity to version 37.0 or later to address the input validation vulnerability. Prior to upgrade, assess current deployment version and verify upgrade compatibility in a staging environment.

Recommended fix High confidence

Pexip Infinity 37.0

  1. Verify the current Pexip Infinity version by accessing the admin interface or running the command line management tool
  2. Review the Pexip Infinity upgrade documentation at docs.pexip.com for version 37.0 upgrade requirements
  3. Ensure all prerequisite system requirements are met for version 37.0
  4. Create a full backup of the current Pexip Infinity configuration and database
  5. Schedule a maintenance window as upgrades may require service interruption
  6. Download the Pexip Infinity version 37.0 software from the official Pexip download portal
  7. Follow the official upgrade procedure documented at docs.pexip.com for applying the version 37.0 update
  8. After upgrade, verify the system is operational and the version is correctly reported as 37.0
Caveat Review Pexip Infinity 37.0 release notes for any feature changes or configuration requirements that may differ from previous versions

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

Fix this in Pexip Infinity Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
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,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32095 — 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-32095 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