CVE-2025-14821: Libssh: libssh: insecure default configuration leads to local man-in-the-middle attacks on windows
A flaw was found in libssh. This vulnerability allows local man-in-the-middle attacks, security downgrades of SSH (Secure Shell) connections, and manipulation of trusted host information, posing a significant risk to the confidentiality, integrity, and availability of SSH communications via an insecure default configuration on Windows systems where the library automatically loads configuration files from the C:\etc directory, which can be created and modified by unprivileged local users.
Security readout for executives and security teams
Plain-English summary
CVE-2025-14821 is a high-severity libssh Windows configuration issue. A local low-privileged user may influence SSH behavior because libssh can automatically load configuration from C:\etc, a path unprivileged users may create or modify. That can undermine SSH confidentiality and integrity on affected systems.
Executive priority
Treat as a priority for Windows environments using libssh, especially packaged images or tools that initiate SSH connections. The issue is local-access dependent, but it can compromise SSH trust and session security once abused.
Technical view
The issue is classified as CWE-427 and scored CVSS 7.8. The attack vector is local with low privileges and no user interaction. The described impact is local man-in-the-middle, SSH security downgrade, and trusted-host manipulation when vulnerable Windows libssh configurations load attacker-controlled files from C:\etc.
Likely exposure
Exposure is most likely on Windows systems or images using affected libssh builds with the insecure default configuration. The provided Red Hat data marks Red Hat Hardened Images libssh-main 0.12.0-1.1.hum1 affected, while listed RHEL and OpenShift products are unaffected.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation evidence. Exploitation requires local user access, but successful abuse could affect SSH trust decisions and connection security for processes using the vulnerable libssh configuration path.
Researcher notes
Evidence is source-limited. The bundle identifies the insecure Windows default configuration and one affected Red Hat package entry, but does not provide broader upstream version ranges beyond referenced libssh security releases. Avoid assuming remote exploitability or active exploitation.
Mitigation direction
Identify Windows systems and images using libssh or Red Hat libssh-main.
Apply vendor-provided libssh security updates where applicable.
Follow Red Hat RHSA-2026:7067 and libssh release guidance.
Restrict unprivileged creation or modification of C:\etc where feasible.
Review SSH trusted-host data after remediation.
Validation and detection
Inventory libssh package names and versions across Windows workloads and images.
Check whether C:\etc exists and whether standard users can modify it.
Confirm affected Red Hat Hardened Images are updated or replaced.
Verify listed RHEL and OpenShift assets match unaffected entries.
Review vendor advisories for exact fixed builds before closure.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · low confidence lookup
CWE-427: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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.
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.
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.
1CVSS vectors
5Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-427 · source CWE mapping
Uncontrolled Search Path Element
Uncontrolled Search Path Element represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.