dbcve.org
Out-of-bounds ReadWeakness · CWE-125

CVE-2026-53566

MEDIUM · 6.8 CVSS v4.0 Published 2026-07-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Zero-click 5 weeks old

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
Out-of-bounds read vulnerability in Citrix Citrix Secure Access Client for Windows. This issue affects Citrix Secure Access Client for Windows: before 26.6.1.20.

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

Out-of-bounds read vulnerability in Citrix Secure Access Client for Windows allows reading memory beyond intended buffer boundaries, potentially leading to information disclosure. This memory safety issue exists in versions prior to 26.6.1.20.

MitigationUpdate Citrix Secure Access Client for Windows to version 26.6.1.20 or later to address the vulnerability.

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

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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
    Check the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry with DisplayName containing 'Citrix Secure Access Client', or look in Program Files for a Citrix Secure Access Client folder.
    Affected if No Citrix Secure Access Client installation is found on the system.
  2. Locate the main executable
    Open File Explorer and navigate to Program Files or Program Files (x86), then search for files named 'Citrix Secure Access Client.exe' or similar executable files from Citrix.
    Affected if The Citrix Secure Access Client executable cannot be located on the system.
  3. Retrieve the installed version number
    Right-click the main Citrix Secure Access Client executable, select Properties, then go to the Details tab to view the File Version. Alternatively, run 'Get-ItemProperty' in PowerShell on the executable path to retrieve version info.
    Affected if The version cannot be determined from the executable.
  4. Compare version against the affected range
    Parse the version number found in the previous step and compare it numerically to version 26.6.1.20. The affected versions are any release prior to 26.6.1.20.
    Affected if The installed version is older than 26.6.1.20 (e.g., 26.6.0.0, 25.x.x.x, etc.).

The system is affected if Citrix Secure Access Client for Windows is installed with a version number lower than 26.6.1.20.

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

Update Citrix Secure Access Client for Windows to version 26.6.1.20 or later to address the vulnerability.

Recommended fix Moderate confidence

Citrix Secure Access Client for Windows version 26.6.1.20 or later

  1. Identify the current version of Citrix Secure Access Client for Windows by checking the application or using 'Add or Remove Programs'
  2. Navigate to the Citrix support website (support.citrix.com) and download version 26.6.1.20 or later of Citrix Secure Access Client for Windows
  3. Close any running instances of Citrix Secure Access Client
  4. Run the installer and follow the on-screen prompts to upgrade the application
  5. Restart your system if prompted by the installer
  6. Verify the installation was successful by checking the version in 'Add or Remove Programs' and confirming it shows version 26.6.1.20 or later

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53566 — 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-2026-53566 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