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-113610 Overview
CVE-2026-113610 is an authorization bypass vulnerability in Xen Orchestra versions before 6.9.0. The flaw exists in the xo-serveruser.set API method, which fails to verify that the caller owns the target account before applying preference changes. Low-privileged authenticated users can supply an arbitrary target user id and modify another user's preferences. Attackers can delete the preferences.otp TOTP secret to disable two-factor authentication, corrupt it to lock legitimate users out, or overwrite stored xsCredentials and sshKeys. The weakness is classified under CWE-639: Authorization Bypass Through User-Controlled Key.
Critical Impact
Any authenticated user can disable multi-factor authentication on administrator accounts and overwrite stored XenServer credentials and SSH keys.
Affected Products
- Xen Orchestra (xo-server) versions prior to 6.9.0
- Vates xen-orchestra repository builds using the vulnerable user.set API handler
- Deployments exposing the xo-server JSON-RPC API to multi-tenant users
Discovery Timeline
- 2026-10-20 - CVE-2026-113610 published to NVD
- 2026-10-20 - Last updated in NVD database
Technical Details for CVE-2026-113610
Vulnerability Analysis
The user.set API in xo-server accepts an id parameter identifying the user record to modify. The handler applies updates to the target user without validating that the authenticated caller matches the target id or holds an administrative role. As a result, a user with only standard permissions can call user.set against any other account, including administrators. Preference fields are not restricted to self-service data, so sensitive values such as TOTP seeds, cached XenServer credentials (xsCredentials), and SSH keys (sshKeys) are all reachable through the same code path.
Root Cause
The handler relies on a client-supplied identifier as the authorization key, which is the exact pattern described in CWE-639. Vulnerable logic can be reviewed in the upstream user API source. The patch adds a safeguard that rejects dangerous property keys and tightens handling of untrusted inputs, as shown in the upstream fix commit.
Attack Vector
Exploitation requires only a valid low-privileged Xen Orchestra account and network access to the xo-server API. The attacker issues a user.set JSON-RPC call containing another user's id and a crafted preferences object. Setting preferences.otp to an empty or malformed value disables or breaks two-factor authentication. Supplying attacker-controlled xsCredentials or sshKeys can redirect subsequent operations through infrastructure the attacker controls.
// Patch excerpt - adds a reserved-key denylist to block prototype pollution
// via untrusted preference and parser inputs.
+// reserved names that would let untrusted data (a vmsd/vmx line or a SOAP
+// response) pollute Object.prototype (e.g. "__proto__.polluted = "x"") instead
+// of just setting a data property
+export const UNSAFE_KEYS = new Set(['__proto__', 'constructor', 'prototype'])
Source: GitHub Commit 3dbf873
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-113610
Indicators of Compromise
- user.set API calls where the id parameter does not match the authenticated session's user id.
- Unexpected removal, resetting, or modification of preferences.otp on administrator accounts.
- New or altered xsCredentials or sshKeys entries on user records that did not perform the change themselves.
Detection Strategies
- Parse xo-server audit logs for user.set invocations and correlate the caller id with the target id.
- Alert on any TOTP disablement event not initiated through the user's own preferences UI.
- Baseline normal preference-update frequency per account and flag outliers that modify authentication fields.
Monitoring Recommendations
- Forward xo-server logs to a centralized SIEM and enable alerting on administrator preference changes.
- Track failed logins immediately following TOTP changes, which can indicate account lockout from a corrupted secret.
- Review access logs for low-privilege accounts issuing high volumes of API calls against the user endpoint.
How to Mitigate CVE-2026-113610
Immediate Actions Required
- Upgrade Xen Orchestra xo-server to version 6.9.0 or later as described in GHSA-mc4m-hc98-rhmv.
- Audit all user accounts for unexpected changes to preferences.otp, xsCredentials, and sshKeys.
- Force re-enrollment of two-factor authentication for administrator accounts after patching.
Patch Information
Vates addressed the issue in Xen Orchestra 6.9.0. Technical details and the upstream fix are published in the VulnCheck advisory and the GitHub Security Advisory GHSA-mc4m-hc98-rhmv. The remediation enforces that non-administrative callers may only modify their own user record and adds the UNSAFE_KEYS denylist to reject prototype-pollution payloads.
Workarounds
- Restrict xo-server API access to trusted administrators until the upgrade is completed.
- Place Xen Orchestra behind a reverse proxy that filters user.set requests where the request body id differs from the authenticated principal.
- Rotate stored XenServer credentials and SSH keys for any account whose preferences may have been altered.
# Verify the installed xo-server version and upgrade if below 6.9.0
npm ls xo-server
yarn --cwd /opt/xen-orchestra/packages/xo-server upgrade
systemctl restart xo-server
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

