CVE-2026-9547

HIGHPre-NVD 7.47.4
EchelonGraph scoreMEDIUM confidence

Score 7.4 from GitHub Security Advisory (severity: HIGH) published 2026-07-03. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — Patch released this weekElevated
7.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.4Exploit: Elevated riskExposed: 0

A fix is available — apply it.

When a libcurl-based application performs transfers via SCP:// or SFTP:// and utilizes the CURLOPT_SSH_KEYFUNCTION callback, it may silently accept an untrusted server. This vulnerability occurs when a server presents a host key type that does not match the specific key type already recorded for that host in the known_hosts file. Instead of rejecting the mismatch, the callback mechanism fails to properly enforce the restriction, allowing the connection to succeed without warning and risking a potential man-in-the-middle attack.

CVSS v3
7.4
EG Score
7.4(medium)
EG Risk
49(Track*)
EG Risk 49/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
Severity74% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

July 3, 2026

Last Modified

July 7, 2026

Advisory Details (3)

Auto-updated Jul 7, 2026
No patch confirmed yet.
generic

curl - SSH improper host validation - CVE-2026-9547

https://curl.se/docs/CVE-2026-9547.html

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibcurl4-openssl-dev (7.35.0-1ubuntu2.20+esm20) @ trusty2026-08-20ubuntu
redhatcurl-0:8.12.1-4.el10_2.32026-08-17redhat
redhatcurl-0:7.76.1-40.el9_8.52026-08-17redhat
redhatrust-main-1.96.1-1.hum12026-07-02redhat
redhatcurl-main-8.21.0-0.1.hum12026-06-24redhat

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

(5 across 5 ecosystems)
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
curl8.21.0-r0
Debian:11(1)
PackageVulnerable rangeFixed inDependents
curl7.74.0-1.3 ... 8.9.1-2~bpo12+1 (219 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
curl7.88.1-10 ... 8.9.1-2~bpo12+1 (174 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
curl8.14.1-2 ... 8.21.0~rc3-1+exp1 (74 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
curl8.14.1-2 ... 8.21.0~rc1-1+exp1 (59 versions)8.21.0~rc2-1

Additional Vendor Advisories

(1)

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 40× in last 7d / 161× 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 218 total refreshes for this CVE.

  1. 2026-08-20 22:56 UTCEPSS rescore
  2. 2026-08-20 15:51 UTCVendor advisory
  3. 2026-08-20 15:51 UTCGHSA enrichment
  4. 2026-08-20 03:56 UTCEG score recompute
  5. 2026-08-20 03:56 UTCVendor advisory
  6. 2026-08-20 03:56 UTCGHSA enrichment
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 10:50 UTCVendor advisory
  9. 2026-08-19 10:50 UTCGHSA enrichment
  10. 2026-08-18 23:21 UTCEG score recompute
  11. 2026-08-18 23:21 UTCVendor advisory
  12. 2026-08-18 23:21 UTCGHSA enrichment
  13. 2026-08-18 13:49 UTCEPSS rescore
  14. 2026-08-18 11:46 UTCVendor advisory
  15. 2026-08-18 11:46 UTCGHSA enrichment
  16. 2026-08-17 22:49 UTCEG score recompute
  17. 2026-08-17 22:49 UTCVendor advisory
  18. 2026-08-17 22:49 UTCGHSA enrichment
  19. 2026-08-17 13:47 UTCEPSS rescore
  20. 2026-08-17 06:06 UTCVendor advisory
  21. 2026-08-17 06:06 UTCGHSA enrichment
  22. 2026-08-16 18:13 UTCEG score recompute
  23. 2026-08-16 18:13 UTCVendor advisory
  24. 2026-08-16 18:13 UTCGHSA enrichment
  25. 2026-08-16 14:56 UTCEPSS rescore
Show 75 more
  1. 2026-08-16 06:46 UTCEG score recompute
  2. 2026-08-16 06:46 UTCVendor advisory
  3. 2026-08-16 06:46 UTCGHSA enrichment
  4. 2026-08-16 02:15 UTCEPSS rescore
  5. 2026-08-15 19:21 UTCVendor advisory
  6. 2026-08-15 19:21 UTCGHSA enrichment
  7. 2026-08-15 07:55 UTCEG score recompute
  8. 2026-08-15 07:55 UTCVendor advisory
  9. 2026-08-15 07:55 UTCGHSA enrichment
  10. 2026-08-15 01:31 UTCEPSS rescore
  11. 2026-08-14 19:39 UTCVendor advisory
  12. 2026-08-14 19:39 UTCGHSA enrichment
  13. 2026-08-14 08:13 UTCEG score recompute
  14. 2026-08-14 08:13 UTCVendor advisory
  15. 2026-08-14 08:13 UTCGHSA enrichment
  16. 2026-08-13 22:00 UTCEPSS rescore
  17. 2026-08-13 20:47 UTCVendor advisory
  18. 2026-08-13 20:47 UTCGHSA enrichment
  19. 2026-08-13 09:21 UTCVendor advisory
  20. 2026-08-13 09:21 UTCGHSA enrichment
  21. 2026-08-12 21:55 UTCEG score recompute
  22. 2026-08-12 21:55 UTCVendor advisory
  23. 2026-08-12 21:55 UTCGHSA enrichment
  24. 2026-08-12 13:51 UTCEPSS rescore
  25. 2026-08-12 10:29 UTCVendor advisory
  26. 2026-08-12 10:29 UTCGHSA enrichment
  27. 2026-08-11 23:03 UTCEG score recompute
  28. 2026-08-11 23:03 UTCVendor advisory
  29. 2026-08-11 23:03 UTCGHSA enrichment
  30. 2026-08-11 13:43 UTCEPSS rescore
  31. 2026-08-11 11:37 UTCVendor advisory
  32. 2026-08-11 11:37 UTCGHSA enrichment
  33. 2026-08-11 00:11 UTCEG score recompute
  34. 2026-08-11 00:11 UTCVendor advisory
  35. 2026-08-11 00:11 UTCGHSA enrichment
  36. 2026-08-11 00:00 UTCEPSS rescore
  37. 2026-08-10 12:45 UTCVendor advisory
  38. 2026-08-10 12:45 UTCGHSA enrichment
  39. 2026-08-10 01:19 UTCVendor advisory
  40. 2026-08-10 01:19 UTCGHSA enrichment
  41. 2026-08-09 13:53 UTCEG score recompute
  42. 2026-08-09 13:53 UTCVendor advisory
  43. 2026-08-09 13:53 UTCGHSA enrichment
  44. 2026-08-09 13:47 UTCEPSS rescore
  45. 2026-08-09 02:28 UTCEG score recompute
  46. 2026-08-09 02:28 UTCVendor advisory
  47. 2026-08-09 02:28 UTCGHSA enrichment
  48. 2026-08-08 16:37 UTCEPSS rescore
  49. 2026-08-08 15:02 UTCVendor advisory
  50. 2026-08-08 15:02 UTCGHSA enrichment
  51. 2026-08-08 03:35 UTCEG score recompute
  52. 2026-08-08 03:35 UTCVendor advisory
  53. 2026-08-08 03:35 UTCGHSA enrichment
  54. 2026-08-07 16:30 UTCEPSS rescore
  55. 2026-08-07 16:09 UTCVendor advisory
  56. 2026-08-07 16:09 UTCGHSA enrichment
  57. 2026-08-07 04:44 UTCVendor advisory
  58. 2026-08-07 04:44 UTCGHSA enrichment
  59. 2026-08-06 17:17 UTCEG score recompute
  60. 2026-08-06 17:17 UTCVendor advisory
  61. 2026-08-06 17:17 UTCGHSA enrichment
  62. 2026-08-06 13:47 UTCEPSS rescore
  63. 2026-08-06 05:51 UTCEG score recompute
  64. 2026-08-06 05:51 UTCVendor advisory
  65. 2026-08-06 05:51 UTCGHSA enrichment
  66. 2026-08-05 19:17 UTCEPSS rescore
  67. 2026-08-05 18:25 UTCVendor advisory
  68. 2026-08-05 18:25 UTCGHSA enrichment
  69. 2026-08-05 06:59 UTCVendor advisory
  70. 2026-08-05 06:59 UTCGHSA enrichment
  71. 2026-08-04 17:12 UTCEG score recompute
  72. 2026-08-04 17:12 UTCVendor advisory
  73. 2026-08-04 17:12 UTCGHSA enrichment
  74. 2026-08-04 15:10 UTCEPSS rescore
  75. 2026-08-04 10:39 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-9547?
CVE-2026-9547 is a high vulnerability published on July 3, 2026. When a libcurl-based application performs transfers via SCP:// or SFTP:// and utilizes the CURLOPTSSHKEYFUNCTION callback, it may silently accept an untrusted server. This vulnerability occurs when a server presents a host key type that does not match the specific key type already recorded for that…
When was CVE-2026-9547 disclosed?
CVE-2026-9547 was first published in the National Vulnerability Database on July 3, 2026, with the most recent update on July 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9547 actively exploited?
CVE-2026-9547 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 74.5% of all scored CVEs.
What is the CVSS score of CVE-2026-9547?
CVE-2026-9547 has a CVSS v3.1 base score of 7.4 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-9547?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9547, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-9547

Explore →

Is Your Infrastructure Affected by CVE-2026-9547?

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