VulnerabilityPublished 25 Dec 2025Updated 26 Dec 2025

CVE-2025-32095: Pexip Infinity · Reachable Assertion

Affects Pexip InfinitySource CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Pexip Infinity	Affected =0	Fixed in–

AI-suggested

Monitor network traffic for unusual or malformed signalling messages targeting Pexip Infinity services to detect potential exploitation attempts.
Implement network-level protections such as firewalls or intrusion prevention systems (IPS) with signatures or heuristics to block suspicious signalling traffic.
Restrict access to Pexip Infinity signalling ports to trusted networks and users where feasible, using network segmentation and access control lists.
Prepare for rapid deployment of vendor patches by establishing a patch management process specifically for Pexip Infinity once updates become available.
Conduct regular backups and ensure failover or redundancy mechanisms are in place to maintain service availability during potential DoS incidents.
Engage with Pexip support or vendor channels to receive timely vulnerability disclosures and remediation guidance.
Educate IT and security teams about this vulnerability to increase awareness and readiness for incident response.
Consider deploying application-layer gateways or proxies that can validate signalling messages before forwarding them to Pexip Infinity servers.

Description

CVE-2025-32095 is a high-severity vulnerability in Pexip Infinity versions prior to 37.0, caused by improper input validation in the signalling component. A remote attacker can send a specially crafted signalling message that triggers a reachable assertion failure, causing the software to abort and resulting in a denial of service (DoS). This vulnerability requires no authentication or user interaction and can be exploited over the network. While it does not impact confidentiality or integrity, the availability impact is significant. No known exploits are currently reported in the wild. European organizations using Pexip Infinity for video conferencing or unified communications should prioritize patching once updates are available. Countries with high adoption of Pexip Infinity and critical reliance on video collaboration tools are at greater risk. Mitigation involves monitoring network traffic for anomalous signalling messages and applying vendor patches promptly upon release.

Impact

For European organizations, the primary impact is denial of service on Pexip Infinity platforms, which can disrupt video conferencing, remote meetings, and unified communications. This can affect business continuity, especially in sectors like finance, healthcare, government, and critical infrastructure where reliable communication is essential. The disruption could also impact cross-border collaboration within the EU and with external partners. Since the vulnerability requires no authentication, attackers can exploit it remotely, increasing the risk of widespread service outages. Organizations heavily dependent on Pexip Infinity for daily operations may face operational delays, loss of productivity, and potential reputational damage. The lack of confidentiality or integrity impact limits data breach concerns, but availability loss alone can have significant operational consequences. The absence of known exploits in the wild provides a window for proactive mitigation before active attacks emerge.

Summary

CVE-2025-32095 is a vulnerability identified in Pexip Infinity, a widely used video conferencing and collaboration platform. The flaw stems from improper input validation in the signalling protocol handling, classified under CWE-617 (Reachable Assertion). Specifically, the software contains assertions that are reachable and can be triggered by crafted signalling messages sent remotely without authentication or user interaction. When exploited, the assertion failure causes the Pexip Infinity service to abort unexpectedly, leading to a denial of service condition. The CVSS v3.1 base score is 7.5, reflecting high severity due to network attack vector, low attack complexity, no privileges required, and no user interaction needed. The vulnerability affects all versions before 37.0, and no patches are currently linked, indicating that a fix is anticipated but not yet released. Although the vulnerability does not compromise confidentiality or integrity, the availability impact can disrupt critical communication services, especially in enterprise environments relying on Pexip for real-time collaboration. No known exploits have been observed in the wild, but the ease of exploitation and potential impact warrant immediate attention. The vulnerability highlights the importance of robust input validation in signalling protocols to prevent assertion failures that can crash services.

CWE-617Reachable Assertion (opens in a new tab)
Base weakness
The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.
Implementation
Make sensitive open/close operation non reachable by directly user-controlled data (e.g. open/close resources)
Implementation · Input Validation
Perform input validation on user data.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

docs.pexip.com/admin/security_bulletins.htm (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 1 Jan 2026, 22:39 UTC

WeaknessesCWE-617

Technical details

References

Community reviews

Related threats