A flaw in libcurl makes it wrongly reuse an HTTP connection setup for a given hostname using Negotiate authentication, when the initial request is done using empty credentials. This can make user B's request get sent over user A's previously authenticated connection.
CVE-2026-19931
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-06. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.8
- EG Score
- 9.8(high)
- EG Risk
- 75(Attend)EG Risk 75/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity98% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 1%
- EPSS %ILE
- 66%
- KEV
- Not listed
Published
September 6, 2026
Last Modified
September 15, 2026
Advisory Details (3)
Auto-updated Sep 15, 2026curl - Negotiate ambient user conn reuse - CVE-2026-19931
https://curl.se/docs/CVE-2026-19931.htmlVendor Advisories for CVE-2026-19931(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(5 across 5 ecosystems)
Alpine:v3.23(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| curl | — | 8.22.0-r0 | — |
Alpine:v3.24(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| curl | — | 8.22.0-r0 | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| curl | 7.88.1-10 ... 8.9.1-2~bpo12+1 (179 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| curl | 8.14.1-2 ... 8.22.0~rc3-1+exp1 (79 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| curl | 8.14.1-2 ... 8.22.0~rc3-1+exp1 (73 versions) | — | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 100× in last 7d / 151× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
Showing the most recent 100 of 151 total refreshes for this CVE.
- 2026-09-19 03:47 UTCVendor advisory
- 2026-09-19 03:47 UTCGHSA enrichment
- 2026-09-18 23:56 UTCVendor advisory
- 2026-09-18 23:56 UTCGHSA enrichment
- 2026-09-18 20:06 UTCEG score recompute
- 2026-09-18 20:06 UTCVendor advisory
- 2026-09-18 20:06 UTCGHSA enrichment
- 2026-09-18 19:27 UTCEPSS rescore
- 2026-09-18 16:14 UTCVendor advisory
- 2026-09-18 16:14 UTCGHSA enrichment
- 2026-09-18 11:45 UTCVendor advisory
- 2026-09-18 11:45 UTCGHSA enrichment
- 2026-09-18 07:54 UTCVendor advisory
- 2026-09-18 07:54 UTCGHSA enrichment
- 2026-09-18 04:03 UTCVendor advisory
- 2026-09-18 04:03 UTCGHSA enrichment
- 2026-09-18 00:12 UTCVendor advisory
- 2026-09-18 00:12 UTCGHSA enrichment
- 2026-09-17 20:21 UTCEG score recompute
- 2026-09-17 20:21 UTCVendor advisory
- 2026-09-17 20:21 UTCGHSA enrichment
- 2026-09-17 14:40 UTCVendor advisory
- 2026-09-17 14:40 UTCGHSA enrichment
- 2026-09-17 10:49 UTCVendor advisory
- 2026-09-17 10:49 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-09-17 06:50 UTCVendor advisory
- 2026-09-17 06:50 UTCGHSA enrichment
- 2026-09-17 02:59 UTCVendor advisory
- 2026-09-17 02:59 UTCGHSA enrichment
- 2026-09-16 22:30 UTCVendor advisory
- 2026-09-16 22:30 UTCGHSA enrichment
- 2026-09-16 18:35 UTCVendor advisory
- 2026-09-16 18:35 UTCGHSA enrichment
- 2026-09-16 14:45 UTCEG score recompute
- 2026-09-16 14:45 UTCVendor advisory
- 2026-09-16 14:45 UTCGHSA enrichment
- 2026-09-16 14:07 UTCEPSS rescore
- 2026-09-16 10:54 UTCVendor advisory
- 2026-09-16 10:54 UTCGHSA enrichment
- 2026-09-16 07:03 UTCEG score recompute
- 2026-09-16 07:03 UTCVendor advisory
- 2026-09-16 07:03 UTCGHSA enrichment
- 2026-09-16 05:14 UTCEPSS rescore
- 2026-09-16 03:13 UTCVendor advisory
- 2026-09-16 03:13 UTCGHSA enrichment
- 2026-09-15 23:22 UTCVendor advisory
- 2026-09-15 23:22 UTCGHSA enrichment
- 2026-09-15 19:02 UTCVendor advisory
- 2026-09-15 19:02 UTCGHSA enrichment
- 2026-09-15 15:10 UTCVendor advisory
- 2026-09-15 15:10 UTCGHSA enrichment
- 2026-09-15 11:19 UTCVendor advisory
- 2026-09-15 11:19 UTCGHSA enrichment
- 2026-09-15 07:28 UTCVendor advisory
- 2026-09-15 07:28 UTCGHSA enrichment
- 2026-09-15 06:39 UTCVendor advisory
- 2026-09-15 06:39 UTCGHSA enrichment
- 2026-09-15 05:54 UTCEG score recompute
- 2026-09-15 05:54 UTCVendor advisory
- 2026-09-15 05:54 UTCGHSA enrichment
- 2026-09-15 02:03 UTCVendor advisory
- 2026-09-15 02:03 UTCGHSA enrichment
- 2026-09-14 22:12 UTCVendor advisory
- 2026-09-14 22:12 UTCGHSA enrichment
- 2026-09-14 18:21 UTCVendor advisory
- 2026-09-14 18:21 UTCGHSA enrichment
- 2026-09-14 13:44 UTCVendor advisory
- 2026-09-14 13:44 UTCGHSA enrichment
- 2026-09-14 09:53 UTCVendor advisory
- 2026-09-14 09:52 UTCGHSA enrichment
- 2026-09-14 05:57 UTCVendor advisory
- 2026-09-14 05:57 UTCGHSA enrichment
- 2026-09-14 02:06 UTCVendor advisory
- 2026-09-14 02:06 UTCGHSA enrichment
- 2026-09-13 22:16 UTCVendor advisory
- 2026-09-13 22:16 UTCGHSA enrichment
- 2026-09-13 18:25 UTCEG score recompute
- 2026-09-13 18:25 UTCVendor advisory
- 2026-09-13 18:25 UTCGHSA enrichment
- 2026-09-13 16:46 UTCEPSS rescore
- 2026-09-13 14:34 UTCVendor advisory
- 2026-09-13 14:34 UTCGHSA enrichment
- 2026-09-13 10:43 UTCVendor advisory
- 2026-09-13 10:43 UTCGHSA enrichment
- 2026-09-13 06:52 UTCVendor advisory
- 2026-09-13 06:52 UTCGHSA enrichment
- 2026-09-13 03:02 UTCVendor advisory
- 2026-09-13 03:02 UTCGHSA enrichment
- 2026-09-12 23:11 UTCVendor advisory
- 2026-09-12 23:11 UTCGHSA enrichment
- 2026-09-12 19:20 UTCVendor advisory
- 2026-09-12 19:20 UTCGHSA enrichment
- 2026-09-12 15:29 UTCEG score recompute
- 2026-09-12 15:29 UTCVendor advisory
- 2026-09-12 15:29 UTCGHSA enrichment
- 2026-09-12 15:00 UTCEPSS rescore
- 2026-09-12 11:39 UTCVendor advisory
- 2026-09-12 11:39 UTCGHSA enrichment
- 2026-09-12 07:48 UTCVendor advisory
- 2026-09-12 07:48 UTCGHSA enrichment
Frequently asked(5)
What is CVE-2026-19931?
When was CVE-2026-19931 disclosed?
Is CVE-2026-19931 actively exploited?
What is the CVSS score of CVE-2026-19931?
How do I remediate CVE-2026-19931?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-19931
Is Your Infrastructure Affected by CVE-2026-19931?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.