dbcve.org
Xenmobile ServerApplication · Citrix

CVE-2022-26151

HIGH · 7.2 CVSS v3.1 Published 2022-04-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Citrix XenMobile Server 10.12 through RP11, 10.13 through RP7, and 10.14 through RP4 allows Command Injection.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Citrix XenMobile Server contains a command injection vulnerability that allows authenticated remote attackers to execute arbitrary commands on the underlying operating system. The vulnerability affects specific rollup patch versions across 10.12, 10.13, and 10.14 release trains.

MitigationApply the appropriate rollup patch (RP) for each affected version: RP12 for 10.12, RP8 for 10.13, and RP5 for 10.14. Refer to Citrix CTX477296 for complete patch details.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Xenmobile ServerApplication
Affected:= 10.13.0= 10.14.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify XenMobile Server version
    Access the XenMobile Server console or check system information to determine the exact installed version (for example, through the management interface or system configuration files)
    Affected if The installed version is 10.13.0 or 10.14.0, or an unpatched version of 10.12 that has not received the appropriate rollup patch
  2. Check applied rollup patch level
    Verify which rollup patch (RP) is installed on the XenMobile Server. For 10.12, verify RP12 is applied; for 10.13, verify RP8 is applied; for 10.14, verify RP5 is applied
    Affected if The system is running an affected version without the corresponding mitigative rollup patch installed (RP8 for 10.13, RP5 for 10.14, or RP12 for 10.12)
  3. Confirm remote access interface is exposed
    Determine if the XenMobile Server web management interface (MDM or MAM) is accessible from the network
    Affected if The management interface is externally accessible without additional network controls, as the vulnerability allows authenticated remote command execution

The environment is affected if running XenMobile Server version 10.13.0 or 10.14.0 (or an unpatched 10.12) without the corresponding mitigative rollup patch installed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the appropriate rollup patch (RP) for each affected version: RP12 for 10.12, RP8 for 10.13, and RP5 for 10.14. Refer to Citrix CTX477296 for complete patch details.

Recommended fix Moderate confidence

XenMobile Server 10.13 RP8 or later / 10.14 RP5 or later (or migrate to Endpoint Management if on older version)

  1. 1. Back up the XenMobile Server configuration and database before performing any upgrade.
  2. 2. Download the fixed Rollup Patch from Citrix support portal (support.citrix.com) - for version 10.13 upgrade to RP8 or later, for version 10.14 upgrade to RP5 or later.
  3. 3. Schedule a maintenance window as the upgrade will require service downtime.
  4. 4. Stop the XenMobile Server services before applying the patch.
  5. 5. Apply the Citrix XenMobile Server Rollup Patch following the official upgrade documentation.
  6. 6. Verify the services start correctly after the patch is applied.
  7. 7. Test critical XenMobile functionality (enrollment, policy distribution, gateway connections) to confirm the remediation is successful.
  8. 8. Review Citrix advisory for any additional post-upgrade configuration requirements.
Caveat Review Citrix compatibility matrix for any impacted integrations or third-party tools before upgrading; ensure adequate downtime window is scheduled

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Xenmobile Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-26151 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-26151 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data