There's a vulnerability in the libssh package where when a libssh consumer passes in an unexpectedly large input buffer to ssh_get_fingerprint_hash() function. In such cases the bin_to_base64() function can experience an integer overflow leading to a memory under allocation, when that happens it's possible that the program perform out of bounds write leading to a heap corruption. This issue affects only 32-bits builds of libssh.
CVE-2025-4877
Score 4.5 from GitHub Security Advisory published 2025-08-20. a secondary CVSS source baseline 4.5; sources differ by 0.0.
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 4.5
- EG Score
- 4.5(medium)
- EG Risk
- 20(Track)EG Risk 20/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity45% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 10%
- KEV
- Not listed
Published
August 20, 2025
Last Modified
August 31, 2026
Advisory Details (5)
Auto-updated Jun 27, 2026projects/libssh.git - libssh shared repository
https://git.libssh.org/projects/libssh.git/commit/?h=stable-0.11&id=6fd9cc8ce3958092a1aae11f1f2e911b2747732d2376193 – (CVE-2025-4877) CVE-2025-4877 libssh: Write beyond bounds in binary to base64 conversion functions
Affected: Red Hat Enterprise Linux 9
https://bugzilla.redhat.com/show_bug.cgi?id=2376193Affected: Red Hat Enterprise Linux 9.
https://access.redhat.com/errata/RHSA-2026:18683Vendor Advisories for CVE-2025-4877(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(3)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | libssh-gcrypt-dev (0.6.3-4.3ubuntu0.6+esm2) @ xenial | 2026-08-31 | ubuntu |
| ubuntu | libssh-doc (0.11.1-1ubuntu0.1) @ plucky | 2026-08-31 | ubuntu |
| redhat | libssh-0:0.10.4-18.el9 | 2026-05-19 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(4 across 4 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| libssh | 0.9.5-1 ... 0.9.8-0+deb11u1 (6 versions) | 0.9.8-0+deb11u2 | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| libssh | 0.10.5-2, 0.10.5-3, 0.10.5-3+hurd.1, 0.10.6-0+deb12u1 | 0.10.6-0+deb12u2 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| libssh | — | 0.11.2-1 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| libssh | — | 0.11.2-1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(3)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 7× in last 7d / 41× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 201 total refreshes for this CVE.
- 2026-09-19 08:36 UTCOSV refresh
- 2026-09-18 19:27 UTCEPSS rescore
- 2026-09-18 19:27 UTCEPSS rescore
- 2026-09-17 19:29 UTCEPSS rescore
- 2026-09-16 14:07 UTCEPSS rescore
- 2026-09-15 03:09 UTCEPSS rescore
- 2026-09-12 15:00 UTCEPSS rescore
- 2026-09-11 14:52 UTCEPSS rescore
- 2026-09-11 09:36 UTCEPSS rescore
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-08 21:59 UTCEPSS rescore
- 2026-09-07 16:00 UTCEPSS rescore
- 2026-09-07 16:00 UTCEPSS rescore
- 2026-09-06 13:46 UTCEPSS rescore
- 2026-09-05 15:28 UTCEPSS rescore
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:11 UTCEPSS rescore
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-09-01 04:38 UTCEPSS rescore
- 2026-08-31 12:29 UTCEG score recompute
- 2026-08-31 12:29 UTCVendor advisory
- 2026-08-31 12:29 UTCGHSA enrichment
- 2026-08-31 11:40 UTCEG score recompute
- 2026-08-31 11:40 UTCVendor advisory
- 2026-08-31 11:40 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-08-30 19:16 UTCEPSS rescore
- 2026-08-30 01:21 UTCEPSS rescore
- 2026-08-28 21:40 UTCEPSS rescore
- 2026-08-27 14:24 UTCEPSS rescore
- 2026-08-26 14:45 UTCEPSS rescore
- 2026-08-24 14:16 UTCEPSS rescore
- 2026-08-24 09:22 UTCEPSS rescore
- 2026-08-23 00:18 UTCEPSS rescore
- 2026-08-21 23:48 UTCEPSS rescore
- 2026-08-21 13:23 UTCEG score recompute
- 2026-08-21 13:23 UTCVendor advisory
- 2026-08-21 13:23 UTCGHSA enrichment
- 2026-08-21 12:50 UTCEG score recompute
- 2026-08-21 12:50 UTCVendor advisory
- 2026-08-21 12:50 UTCGHSA enrichment
- 2026-08-20 22:54 UTCEPSS rescore
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 13:47 UTCEPSS rescore
- 2026-08-16 14:55 UTCEPSS rescore
- 2026-08-16 02:13 UTCEPSS rescore
- 2026-08-15 01:29 UTCEPSS rescore
- 2026-08-13 21:59 UTCEPSS rescore
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-12 07:47 UTCOSV refresh
- 2026-08-11 13:41 UTCEPSS rescore
- 2026-08-10 23:59 UTCEPSS rescore
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-08 16:36 UTCEPSS rescore
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-05 19:16 UTCEPSS rescore
- 2026-08-04 15:09 UTCEPSS rescore
- 2026-08-04 10:37 UTCEPSS rescore
- 2026-08-03 10:35 UTCEPSS rescore
- 2026-08-02 02:26 UTCEPSS rescore
- 2026-08-01 04:15 UTCEPSS rescore
- 2026-07-30 16:27 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-28 15:35 UTCEPSS rescore
- 2026-07-27 13:25 UTCOSV refresh
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-25 14:17 UTCEPSS rescore
- 2026-07-25 14:17 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 02:57 UTCEG score recompute
- 2026-07-22 14:07 UTCEPSS rescore
- 2026-07-22 14:07 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:07 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 02:28 UTCEPSS rescore
- 2026-07-19 02:28 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 17:02 UTCEPSS rescore
- 2026-07-16 17:02 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 01:59 UTCEPSS rescore
- 2026-07-15 01:59 UTCEPSS rescore
- 2026-07-13 22:29 UTCEPSS rescore
- 2026-07-13 22:29 UTCEPSS rescore
- 2026-07-13 06:12 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-10 07:31 UTCOSV refresh
- 2026-07-09 19:09 UTCEPSS rescore
- 2026-07-09 19:09 UTCEPSS rescore
- 2026-07-08 15:15 UTCEPSS rescore
- 2026-07-07 13:45 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
Frequently asked(5)
What is CVE-2025-4877?
When was CVE-2025-4877 disclosed?
Is CVE-2025-4877 actively exploited?
What is the CVSS score of CVE-2025-4877?
How do I remediate CVE-2025-4877?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-4877
Is Your Infrastructure Affected by CVE-2025-4877?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.