Xen Orchestra before 6.9.0 contains an authorization bypass vulnerability in the xo-server user.set API method that allows low-privileged authenticated users to modify other users' preferences by supplying an arbitrary target user id. Attackers can delete the preferences.otp TOTP secret to disable two-factor authentication, corrupt it to block logins, or overwrite stored xsCredentials and sshKeys.
CVE-2026-113610
MEDIUMPre-NVD 5.45.4Trending — 4 sources updated this week
EchelonGraph scoreHIGH confidence
“—” beside the score: it is equal to the CVSS score beside it.
Score 5.4 from GitHub Security Advisory published 2026-10-20. A secondary CVSS source baseline 5.4; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: GitHub Security Advisory, a secondary CVSS source
5.4EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.4Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 5.4
- EG Score
- 5.4MEDIUMhigh confidence
- EG Risk
- 24EG Risk 24/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity54% × 45%Impact severity (EG Severity): CVSS 5.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0% × 40%No KEV listing, EG-KEV tier or EPSS when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.4%
- EPSS %ILE
- 35th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (5.4): severity, escalated by confirmed exploitation. This CVE's 5.4 is its impact severity (EG Severity), not escalated.
- EG Severity
- 5.4 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.4% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 20, 2026
Last Modified
October 20, 2026
Advisory Details (4)
Auto-updated Oct 20, 2026Patch available. Sources: github, github_commit.
Web page
Xen Orchestra before 6.9.0 Authorization Bypass via user.set API | Advisories | VulnCheck
https://www.vulncheck.com/advisories/xen-orchestra-before-6.9.0-authorization-bypass-via-user-set-apiWeb page
xen-orchestra/packages/xo-server/src/api/user.mjs at f187b7931988e3e5c9ccd58abe730d6b006cc246 · vatesfr/xen-orchestra · GitHub
https://github.com/vatesfr/xen-orchestra/blob/f187b7931988e3e5c9ccd58abe730d6b006cc246/packages/xo-server/src/api/user.mjs#L73-L93GitHub commit Patch Available
commit 3dbf8738f1e6 (vatesfr/xen-orchestra)
Patch available: vatesfr/xen-orchestra xo-lite-v0.26.0 (contains commit 3dbf8738f1e6)
https://github.com/vatesfr/xen-orchestra/commit/3dbf8738f1e682b96ade2074dc84bee02a0c2d48GitHub advisoryMentions a patch (unverified)
Privilege Escalation to Global Administrator via Prototype Pollution through Attacker-Controlled VMware VMX in `vm.importFromEsxi` · Advisory · vatesfr/xen-orchestra · GitHub
https://github.com/vatesfr/xen-orchestra/security/advisories/GHSA-mc4m-hc98-rhmvVendor Advisories for CVE-2026-113610(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 8× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-20 20:26 UTCGHSA enrichmentGHSA-22x8-669x-gh7m · GitHub CVSS 5.4
- 2026-10-20 19:26 UTCEG score recompute
- 2026-10-20 19:26 UTCGHSA enrichmentGHSA-22x8-669x-gh7m · GitHub CVSS 5.4
- 2026-10-20 18:31 UTCEG score recompute
- 2026-10-20 16:30 UTCEG score recompute
- 2026-10-20 15:49 UTCEG score recomputeFirst assessed: 5.4 MEDIUM
- 2026-10-20 15:47 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-113610?
CVE-2026-113610 is a medium-severity vulnerability; its CVE record was published on October 20, 2026. Xen Orchestra before 6.9.0 contains an authorization bypass vulnerability in the xo-server user.set API method that allows low-privileged authenticated users to modify other users' preferences by supplying an arbitrary target user id. Attackers can delete the preferences.otp TOTP secret to disable…
When was CVE-2026-113610 made public?
CVE-2026-113610 was made public on September 30, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on October 20, 2026. EchelonGraph's copy of the record carries a last-modified date of October 20, 2026; the record at its source may have been updated since.
Is CVE-2026-113610 actively exploited?
CVE-2026-113610 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-113610?
CVE-2026-113610 has a CVSS base score of 5.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-113610?
A fix for CVE-2026-113610 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-113610 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-113610
Is Your Infrastructure Affected by CVE-2026-113610?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.