Unknown severity · Source severity not reportedCVE-2026-107928

info leak uploading over WebSockets with GnuTLSCVE-2026-107928

Answer in brief

CVE-2026-107928 records a Unknown severity vulnerability in info leak uploading over WebSockets with GnuTLS. The current sources do not mark it as known exploited. The current feed maps curl/curl (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Oct 20, 2026Updated Oct 20, 2026Source checked Oct 20, 2026First seen by HOL Oct 20, 2026Material review Oct 20, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Not reported

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps curl/curl (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
curl/curlgeneric	>=8.22.0 <=8.22.0 \|\| >=8.21.0 <=8.21.0 \|\| >=8.20.0 <=8.20.0 \|\| >=8.19.0 <=8.19.0 \|\| >=8.18.0 <=8.18.0 \|\| >=8.17.0 <=8.17.0 \|\| >=8.16.0 <=8.16.0 \|\| >=8.15.0 <=8.15.0 \|\| >=8.14.1 <=8.14.1 \|\| >=8.14.0 <=8.14.0 \|\| >=8.13.0 <=8.13.0 \|\| >=8.12.1 <=8.12.1 \|\| >=8.12.0 <=8.12.0 \|\| >=8.11.1 <=8.11.1 \|\| >=8.11.0 <=8.11.0 \|\| >=8.10.1 <=8.10.1 \|\| >=8.10.0 <=8.10.0 \|\| >=8.9.1 <=8.9.1 \|\| >=8.9.0 <=8.9.0 \|\| >=8.8.0 <=8.8.0 \|\| >=8.7.1 <=8.7.1 \|\| >=8.7.0 <=8.7.0 \|\| >=8.6.0 <=8.6.0 \|\| >=8.5.0 <=8.5.0 \|\| >=8.4.0 <=8.4.0 \|\| >=8.3.0 <=8.3.0 \|\| >=8.2.1 <=8.2.1 \|\| >=8.2.0 <=8.2.0 \|\| >=8.1.2 <=8.1.2 \|\| >=8.1.1 <=8.1.1 \|\| >=8.1.0 <=8.1.0 \|\| >=8.0.1 <=8.0.1 \|\| >=8.0.0 <=8.0.0 \|\| >=7.88.1 <=7.88.1 \|\| >=7.88.0 <=7.88.0 \|\| >=7.87.0 <=7.87.0 \|\| >=7.86.0 <=7.86.0	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for curl/curl.
Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

Published upstream
Oct 20, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Oct 20, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Oct 20, 2026

Sources and claim methodology

Upstream source description

When curl is built with GnuTLS, a malicious WebSocket server can make curl send memory past its send buffer. This is due to an out of bounds read following when `gnutls_record_send()` returns a number of bytes sent **greater than the number of bytes it was given to send**. GnuTLS does that after a blocked send.

Quoted source text, attributed separately from HOL analysis.