CVE-2026-0964
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 · uneditedA malicious SCP server can send unexpected paths that could make the client application override local files outside of working directory. This could be misused to create malicious executable or configuration files and make the user execute them under specific consequences. This is the same issue as in OpenSSH, tracked as CVE-2019-6111.
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 confidenceA path traversal vulnerability in the SCP client allows a malicious server to send unexpected path information that tricks the client into writing files outside the intended working directory, potentially overwriting system files, configurations, or creating malicious executables.
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 dataall versions= 4.0= 8.0= 9.0= 10.0< 0.11.4CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed libssh versionRun 'rpm -qa | grep libssh' or 'ssh -V' to determine the libssh library version installed on the systemAffected if The installed version is less than 0.11.4
-
Verify Red Hat Enterprise Linux versionRun 'cat /etc/redhat-release' to check the RHEL versionAffected if The version is 8.0, 9.0, or 10.0 exactly
-
Check if Red Hat Openshift Container Platform 4.0 is in useRun 'oc version' or check cluster configuration to determine if OCP 4.0 is deployedAffected if Openshift Container Platform version 4.0 is installed
-
Determine if SCP client functionality is actively usedReview system logs or configuration for SCP file transfer operations, or check which SSH client binaries are in useAffected if The system uses SCP client to receive files from remote servers
You are affected if your environment uses libssh version below 0.11.4, or runs RHEL 8.0/9.0/10.0, OCP 4.0, or Red Hat Hardened Images, and utilizes SCP client functionality to transfer files from remote servers.
Generated from the published advisory. Verify against your own configuration.
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 · scoped0.11.4
Implement strict path validation on the client side to reject any file paths containing '..' sequences or paths that resolve outside the intended working directory, ensuring all server-sent paths are validated before any file operations occur.
libssh version 0.11.4 or later
- 1. Identify the current libssh version installed on the system using: rpm -q libssh or dpkg -l libssh4
- 2. For Enterprise Linux systems (RHEL 8.0, 9.0, 10.0), update libssh using: sudo dnf update libssh
- 3. For Debian/Ubuntu-based systems, update using: sudo apt update && sudo apt install libssh-4
- 4. For Hardened Images or OpenShift Container Platform 4.0, update the underlying RHEL OS which contains the libssh package
- 5. After updating, verify the new version is installed: rpm -q libssh (should show version 0.11.4 or later)
- 6. Restart any services that use libssh (such as SSH clients or applications that link against libssh) to ensure the updated library is loaded
- 7. Test SCP functionality to ensure the client still works correctly after the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0964 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-0964 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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