Secure Access ClientApplication · Citrix

CVE-2025-1222

MEDIUM · 6.1 CVSS v3.1 Published 2025-02-20
Fix available
A fix is available. Upgrade to 25.01.2 or later.
See remediation →
63/100
Remediation priority · Elevated
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
An attacker can gain application privileges in order to perform limited modification and/or read arbitrary data in Citrix Secure Access Client for Mac

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 · moderate confidence

This is a local privilege escalation vulnerability in Citrix Secure Access Client for Mac where an attacker can gain application-level privileges to perform limited modification and/or read arbitrary data. The vulnerability allows a local attacker to elevate their privileges within the application context.

MitigationApply available vendor patches or updates for Citrix Secure Access Client for Mac. If no patch is immediately available, restrict local user access to the system and monitor for suspicious process activity.

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
Secure Access ClientApplication
Affected:< 25.01.2

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

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

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. Verify Citrix Secure Access Client is installed
    Open Terminal and run: ls /Applications | grep -i 'citrix' or check /Applications folder for 'Citrix Secure Access'
    Affected if The application exists in /Applications
  2. Determine the installed version
    Open Terminal and run: defaults read /Applications/Citrix\ Secure\ Access.app/Contents/Info CFBundleVersion or right-click the app > Get Info to view Version
    Affected if Version displayed is lower than 25.01.2 or the version cannot be determined (older install)
  3. Confirm the application bundle identifier
    Run: mdls -name kCFBundleIdentifier /Applications/Citrix\ Secure\ Access.app 2>/dev/null
    Affected if Bundle identifier indicates Citrix Secure Access Client and version check from step 2 shows < 25.01.2
  4. Check if the application is currently running
    Run: ps aux | grep -i 'Citrix Secure Access' or open Activity Monitor and search for Citrix processes
    Affected if The vulnerable version is running (versions < 25.01.2)
  5. Review application permissions
    Check System Settings > Privacy & Security > Accessibility or run: ls -la /Applications/Citrix\ Secure\ Access.app/Contents/
    Affected if Application has elevated permissions and version is < 25.01.2

If Citrix Secure Access Client is installed and the version is below 25.01.2, the environment is affected by this privilege escalation vulnerability.

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
Upgrade available Upgrade to 25.01.2 or later
Fixed in 25.01.2
Interim mitigation

Apply available vendor patches or updates for Citrix Secure Access Client for Mac. If no patch is immediately available, restrict local user access to the system and monitor for suspicious process activity.

Recommended fix Moderate confidence

25.01.2

  1. Identify the current version of Citrix Secure Access Client installed on the Mac
  2. Navigate to the Citrix support portal at support.citrix.com
  3. Download Citrix Secure Access Client version 25.01.2 or later for Mac
  4. Follow Citrix's standard installation procedure to apply the update

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

Fix this in Secure Access Client Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2025-1222 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