HOL LogoGuard

Explore HOL

  • HOL home
  • AI agent registry
  • AI plugins
  • Open standards
  • HOL members

Guard product

  • Guard overviewLocal security and control for AI agents and the tools they use.
  • FeaturesRuntime protection, policy routing, review, and evidence.

Explore Guard

  • Product previewWalk through Guard surfaces in read-only demo mode.
  • ComparisonCompare Guard with native controls and AI security vendors.

AI tools

  • All AI toolsEvery supported AI tool and how Guard applies policy to it.
  • Codex
  • Claude Code
  • Cursor
  • Antigravity CLI
  • OpenCode
  • Hermes
  • OpenClaw
  • GitHub Copilot CLI
  • Antigravity
  • Kimi
  • Grok
  • Pi / Oh My Pi
  • Zcode

Extensions

  • All extensionsBrowse command and MCP coverage with owners and stated limits.
  • Command coverageShell command protection across clouds, databases, backups, and packages.
  • MCP server coverageSee how Guard maps risk state across MCP tools and servers.
  • Core safetyThe safety floor listings that ship with Guard.
  • Data and resilienceBackup and storage command protection.
  • Cloud and infrastructureAWS, Azure, GCP, Kubernetes, and more.

Security

  • AI security hubSecurity research, advisories, and agent safety coverage.
  • AI tool securitySecurity profiles for each supported coding agent.
  • Safe labsHands-on attack simulations with safe boundaries.
  • Redacted warningsReal blocked actions with sensitive details removed.
  • AdvisoriesCoordinated disclosure reports for AI tooling.
  • Active CVEsSearch active CVEs affecting AI tooling.

Learn

  • Security guidesPractical guides for securing AI agent workflows.
  • DocsInstall, configure, and operate Guard with confidence.
  • ResearchPublished security research, benchmarks, and methodology.

Community

  • ReleasesVersion history, shipped changes and upgrade notes.
  • ContributorsThe people and contributions behind HOL Guard.
  • AffiliatesShare Guard with your audience and earn from referrals.
  • SponsorKeep agent security open: sponsor a project, place a banner, or fund a security initiative.
PricingEnterpriseOpen AppInstall Guard
  1. Guard
  2. Security
  3. CVEs
  4. CVE 2026 0964 libssh improper sanitation of paths received from
HOL Guard

Public security guidance for teams protecting AI harnesses, MCP servers, skills, prompts, and local tool execution.

Install Guard

AI Security

  • Prompt injection
  • MCP security
  • OWASP MCP mapping
  • Supply chain

Resources

  • Trust packet
  • Harness setup
  • Redacted warnings
  • Safe labs

Product

  • Install Guard
  • Pricing
  • Open dashboard
Guard
  • Guard Overview
  • Releases
  • Contributors
  • Install Guard
  • Pricing
Docs
  • Documentation Index
  • Developer Hub
  • API Reference
  • Root OpenAPI
  • Registry OpenAPI
  • Run in Postman
  • Standards
  • Submit ERC-8004 Contract
  • Feature Your Agent
Best Plugins
  • Browse Plugins
  • Plugin Launches
  • Best Claude Plugins
  • Best Codex Plugins
  • Best Grok Plugins
  • Best Kimi Plugins
  • Best DeepSeek Plugins
  • Best Antigravity Plugins
  • Best MCP Servers
  • Best Cursor Plugins
  • Best OpenCode Plugins
Best Agents
  • Best ERC-8004 Agents
  • Best Virtuals Agents
  • Best MCP Servers
  • Best A2A Agents
  • Best x402 Payable
  • All Categories
Community
  • Telegram
  • X
More
  • About HOL
  • Contact
  • Blog
  • GitHub
  • Privacy
  • Terms of Service
Settings

Copyright © 2026 HOL DAO LLC. All rights reserved.

Back to active CVEs
Medium · CVSS 6.3CVE-2026-0964

Libssh: improper sanitation of paths received from scp serversCVE-2026-0964

Answer in brief

CVE-2026-0964 records a Medium severity (CVSS 6.3) vulnerability in Libssh: improper sanitation of paths received from scp servers. The current sources do not mark it as known exploited. The current feed maps Red Hat/libssh (generic), Red Hat/openshift/ose-rhel-coreos-8 (generic), Red Hat/openshift/ose-rhel-coreos-9 (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Mar 26, 2026Updated Sep 1, 2026Source checked Oct 5, 2026First seen by HOL Aug 21, 2026Material review Sep 1, 2026
Upstream Advisory

Key facts

Risk
Medium · CVSS 6.3
Exploitation
Not marked as known exploited
Affected software
9 mapped packages or products
Fix availability
Not reported

Why this deserves its current priority

CVSS is 6.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Red Hat/libssh (generic), Red Hat/openshift/ose-rhel-coreos-8 (generic), Red Hat/openshift/ose-rhel-coreos-9 (generic). Check affected ranges and fixed versions before updating.

Affected products and reported versions
ProductAffected versionsFixed versions
cpe:2.3:a:libssh:libssh:*:*:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:a:redhat:hardened_images:-:*:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:a:redhat:openshift_container_platform:4.0:*:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:redhat:enterprise_linux:10.0:*:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:redhat:enterprise_linux:8.0:*:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:redhat:enterprise_linux:9.0:*:*:*:*:*:*:*Not reportedNot reported
Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Red Hat/libsshgeneric*Not reported
Red Hat/openshift/ose-rhel-coreos-8generic*Not reported
Red Hat/openshift/ose-rhel-coreos-9generic*Not reported

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for Red Hat/libssh, Red Hat/openshift/ose-rhel-coreos-8, Red Hat/openshift/ose-rhel-coreos-9.
  2. 2Review the reported fix. Source-reported workaround: Do not use SCP! SCP is deprecated for several years and will be removed in future releases! If you have to, the application MUST validate the path returned from `ssh_scp_request_get_filename()` is the path the application requested. The libssh does not do any writing in this case.

Evidence timeline and material changes

  1. Published upstream

    Mar 26, 2026

    Evidence: source:cvelist:source_dates:source-dates:record
  2. Source modified

    Sep 1, 2026

    Evidence: source:cvelist:source_dates:source-dates:record
  3. First seen by HOL

    Aug 21, 2026

Sources and claim methodology

  • Source referenceaccess.redhat.com
  • Source referenceaccess.redhat.com
  • Source referenceaccess.redhat.com
  • Source referencebugzilla.redhat.com
  • Source referencelibssh.org
Upstream source description

A 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.

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • Totolink A3002MU File Upload formUploadFile sub_44B250 path traversalAlso CWE-22
  • Arbitrary file write via calcext:data-mappings, sql provider and Firebird backup functionalityAlso CWE-22
  • CVE-2026-89039 CVE RecordAlso CWE-22
  • WordPress Starter Templates plugin <= 4.7.7 - Cross Site Scripting (XSS) vulnerabilitySame generic ecosystem
  • WordPress Presto Player plugin <= 4.5.2 - Cross Site Scripting (XSS) vulnerabilitySame generic ecosystem
  • WordPress JS Help Desk plugin <= 4.0.0 - Insecure Direct Object References (IDOR) vulnerabilitySame generic ecosystem

Record context

Vulnerability class
Path Traversal
EPSS
Not reported
CWE IDs
CWE-22
Source
CVE List V5
Source checked
Oct 5, 2026
References
5 linked sources
Open source record