A later request can use the earlier source

CVE-2026-107929 concerns curl connection reuse when CURLOPT_INTERFACE or `--interface` is set with the `if!`, `host!` or `ifhost!` prefix. The selected binding was not part of the connection reuse key. A later transfer asking for a different source could reuse the existing connection and leave from the earlier transfer’s address.

The curl project rates the issue Low. Versions 8.9.0 through 8.22.0 are affected; 8.23.0 and specified backported releases are fixed. This matters when applications use interface binding to separate traffic or enforce network routing.

Review multi-network clients

Search scripts and application code for `--interface` and CURLOPT_INTERFACE. Check whether one process performs transfers for different network paths or trust zones while connection reuse is enabled.

Review firewall and proxy logs if you need to confirm the network path used by a transfer. A destination may be correct while the source interface is not the one the application requested.

Patch and confirm routing

Upgrade to curl 8.23.0 or the package supplier’s fixed build. Restart long-running processes that use libcurl. Confirm the interface selection on transfers that use each configured prefix.

If you cannot update immediately, curl recommends avoiding the affected interface option. Use that only after the network owner confirms that the service can operate safely without the binding.