CVE-2026-9547

HIGHPre-NVD 7.47.4—
EchelonGraph scoreHIGH 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 — 3 sources updated this weekElevated
7.4
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.4Exploit: NoneExposed: 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(high)
EG Risk
—
EPSS
40.3%
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

HackerOne

https://hackerone.com/reports/3751712
generic
https://curl.se/docs/CVE-2026-9547.json
generic

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

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

Vendor Advisories for CVE-2026-9547(4)

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 / EcosystemFixed in / PatchReleasedSource
ubuntulibcurl4t64 (8.14.1-2ubuntu1.4) @ questing2026-07-16ubuntu
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.

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 12× in last 7d / 58× 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-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:25 UTCEPSS rescore
  3. 2026-07-21 15:25 UTCEPSS rescore
  4. 2026-07-20 17:08 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 02:29 UTCEPSS rescore
  7. 2026-07-18 10:04 UTCEPSS rescore
  8. 2026-07-16 19:48 UTCVendor advisory
  9. 2026-07-16 19:48 UTCGHSA enrichment
  10. 2026-07-16 17:03 UTCEPSS rescore
  11. 2026-07-16 08:21 UTCVendor advisory
  12. 2026-07-16 08:21 UTCGHSA enrichment
  13. 2026-07-15 20:52 UTCVendor advisory
  14. 2026-07-15 20:52 UTCGHSA enrichment
  15. 2026-07-15 16:57 UTCEPSS rescore
  16. 2026-07-15 09:25 UTCVendor advisory
  17. 2026-07-15 09:25 UTCGHSA enrichment
  18. 2026-07-15 02:00 UTCEPSS rescore
  19. 2026-07-14 21:57 UTCVendor advisory
  20. 2026-07-14 21:57 UTCGHSA enrichment
  21. 2026-07-14 10:31 UTCVendor advisory
  22. 2026-07-14 10:31 UTCGHSA enrichment
  23. 2026-07-13 23:05 UTCVendor advisory
  24. 2026-07-13 23:05 UTCGHSA enrichment
  25. 2026-07-13 22:31 UTCEPSS rescore
Show 33 more
  1. 2026-07-13 11:39 UTCVendor advisory
  2. 2026-07-13 11:39 UTCGHSA enrichment
  3. 2026-07-13 06:13 UTCEPSS rescore
  4. 2026-07-13 00:11 UTCVendor advisory
  5. 2026-07-13 00:11 UTCGHSA enrichment
  6. 2026-07-12 12:44 UTCVendor advisory
  7. 2026-07-12 12:44 UTCGHSA enrichment
  8. 2026-07-12 05:46 UTCEPSS rescore
  9. 2026-07-12 01:18 UTCVendor advisory
  10. 2026-07-12 01:18 UTCGHSA enrichment
  11. 2026-07-11 13:52 UTCVendor advisory
  12. 2026-07-11 13:52 UTCGHSA enrichment
  13. 2026-07-11 08:27 UTCEPSS rescore
  14. 2026-07-11 02:26 UTCVendor advisory
  15. 2026-07-11 02:26 UTCGHSA enrichment
  16. 2026-07-10 15:00 UTCVendor advisory
  17. 2026-07-10 15:00 UTCGHSA enrichment
  18. 2026-07-10 03:35 UTCVendor advisory
  19. 2026-07-10 03:34 UTCGHSA enrichment
  20. 2026-07-09 19:10 UTCEPSS rescore
  21. 2026-07-09 16:07 UTCEG score recompute▲ 7.40
  22. 2026-07-09 16:07 UTCVendor advisory
  23. 2026-07-09 16:07 UTCGHSA enrichment
  24. 2026-07-08 15:16 UTCEPSS rescore
  25. 2026-07-07 13:46 UTCEPSS rescore
  26. 2026-07-06 17:36 UTCMITRE cvelistV5CVSS v3 → 7.4 · severity → HIGH
  27. 2026-07-06 16:27 UTCEPSS rescore
  28. 2026-07-06 12:17 UTCVendor advisory
  29. 2026-07-06 12:17 UTCGHSA enrichment
  30. 2026-07-05 02:31 UTCEPSS rescore
  31. 2026-07-03 08:27 UTCEG score recompute
  32. 2026-07-03 08:27 UTCVendor advisory
  33. 2026-07-03 08:26 UTCNVD updatefirst tracked

Related CVEs(same vendor)

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 40.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs