CVE-2026-86410 curl CVE debrief

Who should care

Defenders and administrators using curl in environments with SFTP or SCP redirects should assess exposure and verify configurations. This includes operators, platform administrators, vulnerability management teams, and security teams who need to ensure host verification is properly set. They should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance, and plan vendor-supported updates or mitigations.

Why it matters

CVE-2026-86410 allows bypass of host verification in curl when following redirects to SFTP or SCP, requiring verification and potential compensating controls.

• Verification of curl versions and configurations is necessary to ensure host verification is properly set.
• Exposure assessment is required in environments using curl with SFTP or SCP redirects.
• Compensating controls, such as additional host verification measures, may be necessary.

Technical summary

The curl command line tool has a flaw in its logic that allows bypass of host verification when following redirects to SFTP or SCP. This vulnerability affects multiple versions of curl and requires verification of configurations and potential compensating controls. The vulnerability is caused by the curl command line tool only setting SSH host verification options when interacting directly using SFTP or SCP, and not as a result of following a redirect. Defenders should prioritize verifying curl versions and configurations, especially in environments using SFTP or SCP with redirects.

Defensive priority

Defenders should prioritize verifying curl versions and configurations, especially in environments using SFTP or SCP with redirects.

Recommended defensive actions

• Verify curl versions and configurations, especially in environments using SFTP or SCP with redirects.
• Assess exposure in environments using curl with SFTP or SCP.
• Consider compensating controls, such as additional host verification measures.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The CVE record and source item provide details on the vulnerability, but additional information on exploitation and impact is limited. There is no evidence of exploitation in the wild, but defenders should verify curl versions and configurations, especially in environments using SFTP or SCP with redirects. The source confidence is limited, and further verification is necessary to ensure host verification is properly set.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.