One of the most interesting things about Pexip Infinity is that a meeting can connect to systems that aren’t people sitting in front of webcams. A recording service can join as a connection of its own. Pexip can send a dedicated audio and video stream to an external recording or broadcasting service. The recording destination can be separate from the computers participating in the meeting. Pexip documents streaming indicators and participant list entries, so this is not inherently invisible recording. People in the same meeting can also receive different views.

Pexip incident on October 29, 2026: We have identified an issue that can cause SIP calls over TCP (port 5060) to drop unexpectedly. Affected calls connect normally but typicall Started 4:35 PM UTC, resolved ongoing (● 6m). Affected: Connect for Microsoft Teams Meetings, Connect for Google Meet Meetings, Virtual Meeting Room (VMR) Service.

Virtru and Pexip have partnered to enhance video meeting security with continuous access control, ensuring real-time compliance for defense and government organizations.

Pexip incident on October 7, 2026: We are investigating reports that Microsoft Teams Guest Join calls may fail to connect when dialled from Google Meet hardware devices. Started 12:55 PM UTC, resolved ongoing (● 7m). Affected: Connect for Google Rooms.

Pexip Infinity 30.0 through 40.x before 41.0 is affected by improper input validation in the web server that allows a malicious attacker to render a Pexip Infinity node inaccessible.

Pexip Infinity before 41.0 is affected by improper input validation in the signaling implementation which allows a remote attacker to trigger a software abort resulting in a denial of service. Exploitation of this issue requires accessing a gateway call from a WebRTC/API client.

Pexip Infinity before 38.2, plus 39.0, 39.1 and 40.0, is affected by improper input validation that allows a remote attacker to execute code remotely as an unprivileged user on a Pexip Infinity Conferencing Node.

Pexip Infinity before 38.2, plus 39.0, 39.1 and 40.0, is affected by improper access control on a product-internal API which allows an attacker with local access to a node within a Pexip Infinity installation to execute arbitrary code as an unprivileged user on another Pexip Infinity node.

Pexip Infinity before 38.2, plus 39.0, 39.1 and 40.0, is affected by improper access control on a product-internal API which allows an attacker with local access to a node within a Pexip Infinity installation to execute arbitrary code as an unprivileged user on another Pexip Infinity node.

Pexip Infinity 30.0 through 40.x before 41.0 is affected by improper input validation in the web server that allows a malicious attacker to render a Pexip Infinity node inaccessible.

Pexip Infinity before 38.2, plus 39.0, 39.1 and 40.0, is affected by improper input validation that allows a remote attacker to execute code remotely as an unprivileged user on a Pexip Infinity Conferencing Node.

Pexip Infinity versions before 38.2, plus 39.0, 39.1, and 40.0, contain an improper input validation vulnerability classified as CWE-787 (Out-of-bounds Write). This vulnerability enables a remote attacker to execute code remotely as an unpr

Pexip Infinity before 41.0 is affected by improper input validation in the signaling implementation which allows a remote attacker to trigger a software abort resulting in a denial of service. Exploitation of this issue requires accessing a gateway call from a WebRTC/API client.