VulnerabilityPublished 25 Dec 2025Updated 26 Dec 2025

CVE-2025-32096: 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, 09:08 UTC

CVSS 3.1 base score

7.5High

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 23% 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 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 =33.0 <=37.0	Fixed in–

AI-suggested

1. Upgrade Pexip Infinity to version 37.1 or later as soon as the patch becomes available to address the improper input validation flaw. 2. Until a patch is deployed, restrict network access to the signaling interface using firewalls or network segmentation, allowing only trusted IP addresses or VPN connections. 3. Implement intrusion detection and prevention systems (IDS/IPS) with rules to detect anomalous or malformed signaling messages targeting Pexip Infinity. 4. Monitor system logs and service health metrics for signs of crashes or abnormal restarts indicative of exploitation attempts. 5. Conduct regular vulnerability assessments and penetration tests focusing on communication platforms to identify similar weaknesses. 6. Educate IT and security teams about this vulnerability to ensure rapid response and incident handling. 7. Consider deploying redundancy and failover mechanisms for Pexip Infinity services to minimize downtime in case of an attack. 8. Engage with Pexip support and subscribe to security advisories to stay informed about updates and patches.

Description

CVE-2025-32096 is a high-severity vulnerability in Pexip Infinity versions 33.0 through 37.0 prior to 37.1, caused by improper input validation in the signaling component. This flaw allows an unauthenticated remote attacker to trigger a reachable assertion failure, causing the software to abort and resulting in a denial of service (DoS). The vulnerability does not impact confidentiality or integrity but severely affects availability. Exploitation requires no privileges or user interaction and can be performed remotely over the network. Although no known exploits are currently in the wild, the ease of exploitation and the critical role of Pexip Infinity in video conferencing make this a significant threat. European organizations relying on Pexip for communication services could face service disruptions, impacting business continuity. Mitigation involves promptly upgrading to version 37.

Impact

For European organizations, the primary impact of CVE-2025-32096 is denial of service, which can disrupt video conferencing and collaboration services critical for remote work, customer engagement, and internal communications. This disruption can lead to operational delays, reduced productivity, and potential financial losses, especially for sectors heavily dependent on real-time communications such as finance, healthcare, government, and large enterprises. The inability to maintain stable conferencing services may also affect compliance with regulatory requirements for business continuity and data handling. Additionally, denial of service attacks could be leveraged as part of broader multi-vector campaigns, increasing overall organizational risk. The lack of confidentiality or integrity impact limits the threat to service availability; however, the ease of exploitation and remote attack vector make this a significant concern. European organizations with extensive remote workforce or distributed teams are particularly vulnerable to the operational consequences of this vulnerability.

Summary

CVE-2025-32096 is a vulnerability identified in Pexip Infinity, a widely used video conferencing platform, specifically affecting versions 33.0 through 37.0 before 37.1. The root cause is improper input validation within the signaling component, which processes communication setup messages. This flaw leads to a reachable assertion failure (CWE-617), where the software encounters an unexpected condition and aborts execution. An attacker can exploit this by sending crafted signaling messages remotely without any authentication or user interaction, causing the Pexip Infinity service to crash and become unavailable. The vulnerability impacts availability exclusively, with no direct confidentiality or integrity compromise. The CVSS v3.1 base score is 7.5, reflecting network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), unchanged scope (S:U), no confidentiality or integrity impact (C:N/I:N), and high availability impact (A:H). Although no public exploits have been reported yet, the vulnerability's characteristics suggest it could be weaponized for denial-of-service attacks against organizations relying on Pexip Infinity for critical communications. The lack of a patch at the time of reporting necessitates proactive mitigation strategies. This vulnerability underscores the importance of robust input validation in signaling protocols to maintain service availability in real-time communication platforms.

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