CVE-2025-15079Published Jan 8, 2026 · Jan 8Updated Oct 28
libssh global known_hosts override
curl
Medium5.3Fix available
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| curl curl |
| No fix yet |
| curl curl |
| No fix yet |
| curl curl |
|
curl
| Product | Affected | Fixed in |
|---|---|---|
| curl curl |
| No fix yet |
| curl curl |
| No fix yet |
| curl curl |
|
8.16.08.15.08.14.18.14.08.13.0| No fix yet |
When doing SSH-based transfers using either SCP or SFTP, and setting the known_hosts file, libcurl could still mistakenly accept connecting to hosts *not present* in the specified file if they were added as recognized in the libssh *global* known_hosts file.
From the CVE record · curl
During SCP or SFTP transfers with a specified known_hosts file, libcurl could accept a host absent from that file if the host was recognized in libssh’s global known_hosts file. This bypasses the restriction intended by the specified file; it requires an SSH-based transfer with that configuration.
Engineers running curl or libcurl for SCP or SFTP transfers with a specified known_hosts file should check their deployments; affected versions were not provided.