Findings

CVE-2025-15079

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 t…

Published Jan 8, 2026 · updated Oct 14, 2026 · haxx curl

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.

Timeline

Detection, updates, and resolution for this record.

  1. Jan 8, 2026 · NIST NVD

    Detected

    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.

  2. Oct 14, 2026 · NIST NVD

    Updated

    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.

Affected

  • cpe haxx/curlversion unspecified

Sources

  • CVE.orgCVE-2025-15079

    Official CVE identifier

    cve.org
  • FIRST EPSSCVE-2025-15079

    30-day exploitation probability 0.5%

    first.org
  • NIST NVDCVE-2025-15079

    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.

    nvd.nist.gov

References