Microsoft security update for CVE-2026-3783
🔗 CVE IDs covered (1)
📋 Microsoft's advisory
EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-3783. This page also shows what EchelonGraph holds for CVE-2026-3783, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.
🎯 Affected products5
- azl3 curl 8.11.1-5 on Azure Linux 3.0
- azl3 curl 8.11.1-6 on Azure Linux 3.0
- azl4 curl 8.15.0-15.azl4 on Azure Linux 4.0
- cbl2 curl 8.8.0-8 on CBL Mariner 2.0
- cbl2 curl 8.8.0-8 on CBL-Mariner 2.0
✅ Updates Microsoft lists: 3 updates
3 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.
| KB article | Update | Fixed build |
|---|---|---|
| — | Security Update | 8.11.1-6 |
| — | Security Update | 8.8.0-9 |
| — | Security Update | 0:8.15.0-15.azl4 |
🧭 EchelonGraph on CVE-2026-3783
- EchelonGraph score
- 5.3 MEDIUM
- CISA KEV
- Not listed
- Fix status
- A fix is available — apply it.
Description from the CVE record (CVE.org), as published by its numbering authority
When an OAuth2 bearer token is used for an HTTP(S) transfer, and that transfer performs a redirect to a second URL, curl could leak that token to the second hostname under some circumstances. If the hostname that the first request is redirected to has information in the used .netrc file, with either of the `machine` or `default` keywords, curl would pass on the bearer token set for the first host also to the second one.
Published by curl, the CVE Numbering Authority that assigned CVE-2026-3783, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).