Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-103105 Overview
CVE-2026-103105 is an improper access control vulnerability [CWE-863] in Pexip Infinity that exposes a product-internal API to unauthorized use. An attacker with local access to any node in a Pexip Infinity deployment can execute arbitrary code as an unprivileged user on another node in the same installation. The flaw affects Pexip Infinity versions before 38.2, and versions 39.0, 39.1, and 40.0. The vulnerability requires adjacent network access and no user interaction, and it impacts confidentiality, integrity, and availability across affected nodes.
Critical Impact
An attacker with a foothold on one Pexip Infinity node can pivot to execute arbitrary code on other nodes in the deployment through an unprotected internal API.
Affected Products
- Pexip Infinity versions before 38.2
- Pexip Infinity 39.0 and 39.1
- Pexip Infinity 40.0
Discovery Timeline
- 2026-09-30 - CVE-2026-103105 published to the National Vulnerability Database (NVD)
- 2026-09-30 - Last updated in NVD database
Technical Details for CVE-2026-103105
Vulnerability Analysis
CVE-2026-103105 is an improper authorization flaw [CWE-863] in a product-internal API used for inter-node communication within a Pexip Infinity installation. The API does not adequately verify the authorization of callers originating from within the internal network segment. As a result, an attacker who has already gained access to one node can invoke functions on peer nodes that should be restricted to trusted internal control processes. The outcome is arbitrary code execution as an unprivileged user on the targeted node, providing a foothold for further lateral movement or privilege escalation.
Root Cause
The root cause is missing or insufficient authorization checks on an internal API endpoint. Pexip Infinity nodes trust requests coming from other participants in the installation without enforcing per-caller authentication or authorization. This design assumption breaks once an attacker reaches the internal management or signaling network of any node in the cluster.
Attack Vector
The attack requires adjacent network access, meaning the attacker must reach a Pexip Infinity node over the internal network path that hosts the vulnerable API. Once positioned, the attacker sends crafted requests to the internal API on another node. No credentials and no user interaction are required. Successful exploitation yields arbitrary code execution under an unprivileged service account on the receiving node.
No verified proof-of-concept code has been published. Refer to the Pexip Security Bulletins for vendor-provided technical detail.
Detection Methods for CVE-2026-103105
Indicators of Compromise
- Unexpected process execution by the unprivileged service account used by Pexip Infinity node services.
- Anomalous inter-node traffic patterns on the internal management or signaling API ports of Pexip Infinity nodes.
- New or modified files in Pexip service directories that do not correlate with a documented upgrade or configuration change.
Detection Strategies
- Baseline the internal API traffic between Conferencing Nodes and the Management Node, then alert on request patterns or source nodes that deviate from the baseline.
- Monitor Pexip Infinity system logs for internal API calls that do not correspond to scheduled cluster operations.
- Correlate outbound network connections from Pexip nodes with known-good administrative activity to identify post-exploitation command-and-control.
Monitoring Recommendations
- Enable verbose logging on Pexip Infinity nodes and forward events to a centralized SIEM for retention and correlation.
- Alert on child processes spawned by Pexip service binaries that are not part of the vendor-approved process tree.
- Track network flows between nodes and flag deviations in volume, destination port, or timing that could indicate abuse of the internal API.
How to Mitigate CVE-2026-103105
Immediate Actions Required
- Upgrade Pexip Infinity to a fixed release: version 38.2 or later on the 38.x branch, or a Pexip-designated fixed release for the 39.x and 40.x branches. Consult the Pexip Security Bulletins for the exact fixed builds.
- Restrict network access to Pexip Infinity nodes so that only trusted management workstations and cluster peers can reach node management interfaces.
- Audit all Pexip Infinity nodes for signs of prior compromise before applying the patch, particularly if the installation spans untrusted network segments.
Patch Information
Pexip has addressed CVE-2026-103105 in Pexip Infinity 38.2 and in fixed releases on the 39.x and 40.x branches. Administrators should follow the upgrade procedure documented by Pexip and confirm the running version on every node in the deployment after the upgrade. Refer to the Pexip Security Bulletins for authoritative version and remediation guidance.
Workarounds
- Segment Pexip Infinity nodes on a dedicated internal network with strict firewall rules that limit which hosts can reach node-to-node API ports.
- Remove or isolate any general-purpose hosts from the same network segment as Pexip Infinity nodes to reduce the local-access attack surface.
- Enforce least privilege for administrators who can log in to nodes or adjacent systems, reducing the likelihood of an initial foothold that enables this attack.
# Configuration example: restrict inter-node API access at the host firewall
# Replace 10.10.20.0/24 with the trusted Pexip node subnet
iptables -A INPUT -p tcp --dport 8443 -s 10.10.20.0/24 -j ACCEPT
iptables -A INPUT -p tcp --dport 8443 -j DROP
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

