CVE-2026-59849

LOWPre-NVD 3.13.1—
EchelonGraph scoreHIGH confidence

Score 3.1 from GitHub Security Advisory (severity: LOW) published 2026-07-21. a secondary CVSS source baseline 3.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — Patch released this week
3.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.1Exploit: None knownExposed: 0

A fix is available — apply it.

A flaw was found in libssh. Logic errors in automatic certificate-based public key authentication can cause libssh clients to loop indefinitely when configured certificates are missing or repeatedly rejected by a server, leading to denial of service.

CVSS v3
3.1
EG Score
3.1(high)
EG Risk
14(Track)
EG Risk 14/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 computed
Severity31% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
10%
KEV
Not listed

Published

July 21, 2026

Last Modified

July 22, 2026

References (3)

Vendor Advisories for CVE-2026-59849(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatlibssh-main-0.12.1-4.hum12026-07-21redhat

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.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 19× in last 7d / 19× 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.

  1. 2026-07-26 14:54 UTCEPSS rescore
  2. 2026-07-26 14:54 UTCEPSS rescore
  3. 2026-07-26 10:32 UTCEG score recompute
  4. 2026-07-26 10:32 UTCVendor advisory
  5. 2026-07-26 10:32 UTCGHSA enrichment
  6. 2026-07-25 14:18 UTCEPSS rescore
  7. 2026-07-25 14:18 UTCEPSS rescore
  8. 2026-07-24 14:18 UTCEPSS rescore
  9. 2026-07-24 14:18 UTCEPSS rescore
  10. 2026-07-23 14:18 UTCEPSS rescore
  11. 2026-07-23 14:18 UTCEPSS rescore
  12. 2026-07-23 03:21 UTCEG score recompute
  13. 2026-07-22 23:09 UTCEG score recompute
  14. 2026-07-22 23:09 UTCGHSA enrichment
  15. 2026-07-22 14:08 UTCEPSS rescore
  16. 2026-07-22 14:08 UTCEPSS rescore
  17. 2026-07-21 15:29 UTCEG score recompute
  18. 2026-07-21 14:39 UTCEG score recompute
  19. 2026-07-21 14:37 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-59849?
CVE-2026-59849 is a low vulnerability published on July 21, 2026. A flaw was found in libssh. Logic errors in automatic certificate-based public key authentication can cause libssh clients to loop indefinitely when configured certificates are missing or repeatedly rejected by a server, leading to denial of service.
When was CVE-2026-59849 disclosed?
CVE-2026-59849 was first published in the National Vulnerability Database on July 21, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59849 actively exploited?
CVE-2026-59849 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 90.4% of all scored CVEs.
What is the CVSS score of CVE-2026-59849?
CVE-2026-59849 has a CVSS v3 base score of 3.1 (NVD).
How do I remediate CVE-2026-59849?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59849, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-59849

Explore →

Is Your Infrastructure Affected by CVE-2026-59849?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs