Security readout for executives and security teams
Plain-English summary
A local, low-severity libssh flaw can make affected systems open unsafe files while reading configuration. A malicious local user or bad configuration could target block devices or very large files, disrupting service availability. The supplied evidence does not indicate data theft, data modification, remote exploitation, or active attacks.
Executive priority
Treat this as routine, targeted remediation rather than an emergency. Prioritize multi-user systems, shared build hosts, and services accepting user-influenced libssh configuration. Schedule vendor updates through normal patching, while promptly correcting unsafe configuration permissions or input paths. Escalate if affected components run critical services where even limited downtime has material business impact.
Technical view
CVE-2026-0965 is improper external file or path control during libssh configuration parsing (CWE-73). An authenticated local attacker can supply a malicious configuration file, causing arbitrary file access attempts and limited denial of service. CVSS 3.0 is 3.3: local access, low complexity, low privileges, no user interaction, and low availability impact.
Likely exposure
Exposure is most likely where affected libssh packages on RHEL 8, 9, or 10 parse attacker-controlled configuration. OpenShift 4 RHEL CoreOS 8 and 9 components are also listed as affected. The bundle identifies RHEL 9 package 0.10.4-18.el9 and RHEL 10 package 0.12.0-2.el10. Listed RHEL 6/7 libssh2 packages are unaffected.
Exploitation context
Exploitation requires local access with low privileges or a system configuration that permits untrusted configuration input. The expected consequence is availability disruption rather than confidentiality or integrity loss. CISA KEV status is false, and the supplied sources provide no evidence of active exploitation or a public exploit.
Researcher notes
The source bundle supports local availability impact through unsafe file opening during configuration parsing. It does not establish remote reachability, privilege escalation, confidentiality impact, a public proof of concept, or exploitation in the wild. RHEL 8 and OpenShift entries lack affected version detail. Consult the cited vendor advisories for exact package-specific remediation and applicability.
Mitigation direction
- Review the listed Red Hat errata and apply the applicable vendor-provided update.
- Restrict who can create, modify, or select libssh configuration files.
- Prevent services from consuming configuration supplied by untrusted local users.
- Use least privilege and service isolation to limit access to sensitive files and devices.
Validation and detection
- Inventory installed libssh packages across RHEL 8, 9, and 10 systems.
- Identify OpenShift 4 nodes using the listed RHEL CoreOS 8 or 9 components.
- Compare installed package versions and advisory status with current Red Hat guidance.
- Review configuration ownership, permissions, include paths, and sources for untrusted input.
- Confirm applicable Red Hat updates are installed, then retest dependent services.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-73: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-0965 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Low
- CVSS
- 3.3 (3.0)
- Known Exploited
- No
- Published
Vector: CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L1.81.4redhatVulnerability scoring details
Base CVSS 3.0 score
3.3LowVector: CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- Source timelineredhat
Reported to Red Hat.
- Source timelineredhat
Made public.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- RHSA-2026:18160CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:18683CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/security/cve/CVE-2026-0965CVE reference, redhat · vdb-entry, x_refsource_REDHAT
- RHBZ#2436980CVE reference, redhat · issue-tracking, x_refsource_REDHAT
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
External Control of File Name or Path
External Control of File Name or Path represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.