CVE-2026-59995
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 · uneditedsftp in OpenSSH before 10.4 does not properly constrain the location of downloaded files when "sftp server:/path ." is used with an attacker-controlled server.
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 confidenceThe sftp client in OpenSSH before version 10.4 fails to properly restrict the download location when using the 'sftp server:/path .' syntax. An attacker-controlled SFTP server could exploit insufficient path validation to write files to arbitrary locations on the client system via directory traversal.
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< 10.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
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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.
-
Check OpenSSH/sftp client versionRun 'sftp -V' or 'ssh -V' to display the version number of the installed OpenSSH clientAffected if The version displayed is earlier than 10.4 (e.g., 10.3, 10.2, etc.)
-
Confirm OpenBSD operating systemRun 'uname -a' or check the OS name in the version string output from the previous stepAffected if The system is running OpenBSD and the OpenSSH version is below 10.4
-
Identify sftp usage patternsReview shell history, scripts, or automation that invoke the sftp client, specifically looking for the 'sftp server:/path .' download syntaxAffected if The sftp client is used to download files from remote servers using the 'sftp server:/path .' syntax where the server may be untrusted or externally accessible
-
Check for connections to untrusted SFTP serversInspect known_hosts file, SSH config files, or network logs for SFTP connections to servers outside your organizationAffected if The sftp client connects to SFTP servers that are not fully trusted or are potentially controlled by attackers
You are affected if you run OpenBSD with OpenSSH/sftp client version earlier than 10.4 and use sftp to download files from remote servers using the 'server:/path .' syntax.
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 · scoped10.4
Upgrade OpenSSH to version 10.4 or later to obtain the fixed sftp client that properly constrains download locations.
OpenSSH 10.4
- 1. Check current OpenSSH version: sshd -v or ssh -V
- 2. Verify your operating system's package manager for OpenSSH 10.4 availability
- 3. If available, update via package manager (e.g., apt-get update && apt-get install openssh-client openssh-server, or yum update openssh, etc.)
- 4. If not available in OS repositories, download OpenSSH 10.4 source from official openssh.com/txt/release-10.4
- 5. Compile and install from source following standard OpenSSH build instructions
- 6. Restart sshd service after upgrade: systemctl restart sshd or service sshd restart
- 7. Verify new version is running: ssh -V
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-59995 — 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-59995 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