CVE-2026-12064 curl vulnerability
When a user invokes curl using a schemeless URL combined with `--proto-default` sftp (or scp), a disconnect occurs between the tool layer and libcurl. The tool layer incorrectly infers the URL scheme, which erroneously bypasses the initialization of critical SSH security options like CURLOPT_SSH_HOST_PUBLIC_KEY_SHA256 and CURLOPT_SSH_KNOWNHOSTS. Conversely, the libcurl runtime successfully honors CURLOPT_DEFAULT_PROTOCOL and establishes the connection via SFTP/SCP as specified. Because the tool layer skipped the security configuration, these SSH host verification options are silently omitted, causing curl to connect to an unverified SSH remote host without throwing an error.
Quick answer
haxx curl should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- curl 7.81.0 through 8.20.0
Fixed versions
- curl 8.21.0 or later
How to fix it
CVE-2026-12064 affects haxx curl. The affected range is curl 7.81.0 through 8.20.0. Update to curl 8.21.0 or later. Treat exposed systems first, especially where systems, apps, containers, and tools that use curl or libcurl can be reached. If you suspect abuse, review logs and rotate secrets that may have been exposed.
- Inventory every haxx curl install and note the exact version.
- Compare each install with the affected range: curl 7.81.0 through 8.20.0.
- Update to curl 8.21.0 or later.
- If you cannot patch today, restrict systems, apps, containers, and tools that use curl or libcurl to trusted users and networks.
- Back up the current configuration before changing production systems.
- Review recent logs for errors, crashes, strange admin activity, or unexpected outbound connections.
- Rotate passwords, tokens, and keys if the system may have been exposed or abused.
- Document the change, owner, date, and final version.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm the installed version now matches the fixed guidance: curl 8.21.0 or later.
- Confirm old affected versions are no longer deployed: curl 7.81.0 through 8.20.0.
- Confirm systems, apps, containers, and tools that use curl or libcurl is limited to the smallest needed group.
- Rerun the relevant Fixnx scan or internal check after the change.
- Save logs, screenshots, or package output as proof of the fix.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-12064?
haxx curl versions listed as affected should be reviewed: curl 7.81.0 through 8.20.0.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.