CVE-2026-90822 in IPVPN
Summary
by MITRE • 09/17/2026
FatPipe MPVPN, WARP, and IPVPN appliances running the end-of-life firmware version 10.1.2r60p100 contain an OS command injection vulnerability in the xtremed daemon. An unauthenticated remote attacker with access to the affected management interface can submit crafted input to the AuthFormServlet endpoint, causing authentication data to be processed by a shell and allowing arbitrary commands to execute as root.
The affected management interface is disabled by default and must be affirmatively enabled by the customer before the endpoint becomes reachable. FatPipe recommends restricting management access to trusted administrative networks and using WAN access control lists to limit access to trusted sources.
Customers running the affected end-of-life firmware can contact FatPipe Support for help confirming their firmware version and upgrading to a current supported release at https://www.fatpipeinc.com/support/support, [email protected], or +1 800-724-8521 (option 3).
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Analysis
by VulDB Data Team • 09/17/2026
The vulnerability identified in FatPipe MPVPN, WARP, and IPVPN appliances operating on end-of-life firmware version 10.1.2r60p100 represents a critical OS command injection flaw within the xtremed daemon. This security defect allows an unauthenticated remote attacker to execute arbitrary system commands with root-level privileges by interacting with the AuthFormServlet endpoint of the management interface. The core technical failure lies in the improper handling of user-supplied input during authentication processing, where data is passed directly to a shell interpreter without adequate sanitization or validation. This lack of input filtering enables an adversary to inject malicious command sequences that bypass intended application logic and result in full system compromise. Such vulnerabilities are classically categorized under CWE-78 Improper Neutralization of Special Elements used in an OS Command, highlighting the fundamental failure to neutralize special characters that could alter command structure or introduce new commands into the execution pipeline.
From a tactical perspective, this vulnerability aligns with ATT&CK technique T1059 Command and Scripting Interpreter, specifically where attackers leverage shell access to maintain persistence or escalate privileges on compromised network infrastructure devices. The exploitation of this flaw does not require prior authentication credentials, which significantly lowers the barrier for entry for opportunistic attackers scanning for vulnerable management interfaces across the internet. However, it is crucial to note that the affected management interface is disabled by default in standard configurations. This means that successful exploitation requires a specific configuration state where an administrator has explicitly enabled remote or local access to this administrative endpoint. Consequently, while the technical severity of the vulnerability is extreme due to the root-level impact, the practical risk is heavily dependent on organizational security hygiene regarding the exposure and activation of management services.
The operational impact of successfully exploiting this command injection flaw is severe, as it grants an attacker complete control over the underlying operating system running on the appliance. This level of access allows for the exfiltration of sensitive network configuration data, including VPN keys and routing tables, which can lead to widespread eavesdropping or traffic manipulation across the protected enterprise network. Furthermore, attackers may use this foothold as a pivot point to launch lateral attacks against other internal systems that trust connections from the compromised appliance. The presence of such a high-severity flaw in end-of-life firmware underscores the dangers of maintaining outdated software stacks, as these versions typically lack patches for newly discovered or previously unmitigated vulnerabilities and do not receive security updates from the vendor.
To mitigate this risk, organizations must immediately assess whether their FatPipe appliances are running the affected version 10.1.2r60p100 firmware. If confirmed, the primary remediation step is to upgrade to a current supported release provided by FatPipe Support. Until an upgrade can be performed, strict network segmentation and access control measures must be implemented. This includes restricting management interface access exclusively to trusted administrative networks using firewall rules or WAN access control lists that limit connectivity to known, secure source IP addresses. Additionally, administrators should ensure that the management interface remains disabled if remote administration is not strictly required for operational continuity. Regular audits of firmware versions and adherence to vendor-supported lifecycle policies are essential practices to prevent exposure to such critical command injection vulnerabilities in network infrastructure devices.