CVE-2026-107929

UNRATEDCVSS · not yet scored

Also known asEUVD-2026-105359 (ENISA EUVD) · GHSA-9644-8jhv-gxgm (GitHub Security Advisories)Source: ENISA EUVD

—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
15th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
No SSVC decision: EchelonGraph has not assessed this CVECISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the BOD 26-04 block below.

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 20, 2026

Last Modified

October 22, 2026

References (3)

Vendor Advisories for CVE-2026-107929(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibcurl4t64 (8.18.0-1ubuntu2.8) @ resolute2026-10-22ubuntu
ubuntulibcurl4t64 (8.20.0-2ubuntu11.1) @ stonking2026-10-22ubuntu
redhatcurl-main-8.23.0-0.1.hum12026-10-14redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 8× in last 7d / 18× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  2. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  3. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  4. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  5. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  6. 2026-10-25 14:54 UTCEG score recompute
  7. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  8. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  9. 2026-10-22 17:32 UTCEG score recompute
  10. 2026-10-22 17:32 UTCVendor advisory
  11. 2026-10-22 17:31 UTCGHSA enrichmentGHSA-9644-8jhv-gxgm
  12. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  13. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  14. 2026-10-20 21:26 UTCVendor advisory
  15. 2026-10-20 21:25 UTCNVD update
  16. 2026-10-20 20:42 UTCEG score recompute
  17. 2026-10-20 20:42 UTCVendor advisory
  18. 2026-10-20 20:41 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor)

Frequently asked(4)

What is CVE-2026-107929?
CVE-2026-107929 is a vulnerability whose severity is not yet rated; its CVE record was published on October 20, 2026. 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…
When was the CVE record for CVE-2026-107929 published?
The CVE record for CVE-2026-107929 was published on October 20, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 22, 2026; the record at its source may have been updated since.
Is CVE-2026-107929 actively exploited?
CVE-2026-107929 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (15th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-107929?
A fix for CVE-2026-107929 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-107929 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-107929

Explore →

Is Your Infrastructure Affected by CVE-2026-107929?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs