CVE-2025-14821
No exploitation reported by the sources we read.
- Published2026-04-07
- Fixed in0.12.0
- WeaknessCWE-427
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
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.
Timeline
dates in UTC- 2026-04-0717:16CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2025-14821?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2025-14821?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 0.12 | < 0.12.0 | 0.12.0 | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| — | all versions | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Vendor advisories
libssh: libssh: Insecure default configuration leads to local man-in-the-middle attacks on Windows
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
Fix
- Update Libssh to 0.12.0
- Vendor fix Red Hat Product Security RHSA-2026:7067 · 7 productsFor details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
- Workaround from the vendor Red Hat Product Security RHSA-2026:7067 · 7 productsMitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Advisories and patches
- www.libssh.orgRelease Notes
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- CISA-ADPSSVC decisionnone2026-04-07
- OpenCVESSVC decisionnone—
- CNACVSS 3.17.8read 2026-10-23
- NVDCVSS 3.17read 2026-10-23
- CNAweakness (CWE)CWE-427read 2026-10-23
- FIRST EPSSEPSS score0.1 %2026-10-23
- Microsoft MSRCadvisory—
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
- Published
- 2026-04-07
- Last Modified
- 2026-10-14
- NVD status
- Analyzed
- MSRC Title
- Libssh: libssh: insecure default configuration leads to local man-in-the-middle attacks on windows
Frequently asked questions
What is CVE-2025-14821?
Is CVE-2025-14821 actively exploited?
What is the CVSS score for CVE-2025-14821?
Running libssh? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.