CVE-2026-3783

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

Score 5.3 from GitHub Security Advisory published 2026-03-11. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 4 sources updated this weekElevated
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
55(Attend)
EG Risk 55/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 computed
Severity53% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
39%
KEV
Not listed

Published

March 11, 2026

Last Modified

September 15, 2026

Advisory Details (4)

Auto-updated Aug 6, 2026
No patch confirmed yet.
generic

oss-security - [ADVISORY] curl: CVE-2026-3783: token leak with redirect and netrc

http://www.openwall.com/lists/oss-security/2026/03/11/2
generic

curl - token leak with redirect and netrc - CVE-2026-3783

https://curl.se/docs/CVE-2026-3783.html

Patch Availability(12)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibcurl4t64 (8.14.1-2ubuntu1.2) @ questing2026-09-15ubuntu
ubuntulibcurl4-openssl-dev (7.58.0-2ubuntu3.24+esm8) @ bionic2026-09-15ubuntu
redhatrhui5/rhua-rhel9:17888805812026-09-09redhat
redhatcert-manager/cert-manager-istio-csr-rhel9:17883485942026-09-03redhat
redhatcert-manager/jetstack-cert-manager-rhel9:17883485712026-09-03redhat
redhatcert-manager/cert-manager-operator-rhel9:17883485222026-09-03redhat
redhatdiscovery/discovery-ui-rhel9:17882061962026-08-31redhat
redhatrhui5/rhua-tp-rhel9:17872412602026-08-24redhat
redhatpatch2026-08-19redhat
redhatcurl-0:8.12.1-4.el10_2.32026-08-17redhat
redhatcurl-0:7.76.1-40.el9_8.52026-08-17redhat
redhatcurl-main-8.19.0-3.hum12026-04-07redhat

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.

Affected Packages

(6 across 6 ecosystems)
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
curl8.19.0-r0
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
curl8.19.0-r0
Debian:11(1)
PackageVulnerable rangeFixed inDependents
curl7.74.0-1.3 ... 8.9.1-2~bpo12+1 (219 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
curl7.88.1-10 ... 7.88.1-10+deb12u9 (18 versions)7.88.1-10+deb12u15
Debian:13(1)
PackageVulnerable rangeFixed inDependents
curl8.14.1-2, 8.14.1-2+deb13u1, 8.14.1-2+deb13u2, 8.14.1-2+deb13u2~bpo13+1, 8.14.1-2+deb13u38.14.1-2+deb13u4
Debian:14(1)
PackageVulnerable rangeFixed inDependents
curl8.14.1-2 ... 8.19.0~rc3-1 (36 versions)8.19.0-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

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 13× in last 7d / 33× 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.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-17 19:30 UTCEPSS rescore
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-15 07:25 UTCVendor advisory
  7. 2026-09-15 07:25 UTCGHSA enrichment
  8. 2026-09-15 06:40 UTCEG score recompute
  9. 2026-09-15 06:40 UTCVendor advisory
  10. 2026-09-15 06:40 UTCGHSA enrichment
  11. 2026-09-15 03:11 UTCEPSS rescore
  12. 2026-09-13 16:47 UTCEPSS rescore
  13. 2026-09-12 15:01 UTCEPSS rescore
  14. 2026-09-11 14:53 UTCEPSS rescore
  15. 2026-09-11 09:37 UTCEPSS rescore
  16. 2026-09-10 09:34 UTCEPSS rescore
  17. 2026-09-08 22:00 UTCEPSS rescore
  18. 2026-09-07 16:01 UTCEPSS rescore
  19. 2026-09-06 13:47 UTCEPSS rescore
  20. 2026-09-04 05:06 UTCEPSS rescore
  21. 2026-09-02 20:10 UTCOSV refresh
  22. 2026-09-02 14:12 UTCEPSS rescore
  23. 2026-09-01 13:53 UTCEPSS rescore
  24. 2026-09-01 04:39 UTCEPSS rescore
  25. 2026-08-30 19:17 UTCEPSS rescore
Show 61 more
  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-28 21:41 UTCEPSS rescore
  3. 2026-08-27 14:25 UTCEPSS rescore
  4. 2026-08-26 14:46 UTCEPSS rescore
  5. 2026-08-25 13:49 UTCEPSS rescore
  6. 2026-08-23 00:19 UTCEPSS rescore
  7. 2026-08-21 23:49 UTCEPSS rescore
  8. 2026-08-20 22:55 UTCEPSS rescore
  9. 2026-08-19 17:03 UTCEPSS rescore
  10. 2026-08-18 13:48 UTCEPSS rescore
  11. 2026-08-17 13:47 UTCEPSS rescore
  12. 2026-08-16 14:56 UTCEPSS rescore
  13. 2026-08-16 11:55 UTCEG score recompute
  14. 2026-08-16 11:55 UTCVendor advisory
  15. 2026-08-16 11:55 UTCGHSA enrichment
  16. 2026-08-16 02:14 UTCEPSS rescore
  17. 2026-08-15 01:30 UTCEPSS rescore
  18. 2026-08-14 07:52 UTCEG score recompute
  19. 2026-08-14 07:52 UTCVendor advisory
  20. 2026-08-14 07:52 UTCGHSA enrichment
  21. 2026-08-13 22:00 UTCEPSS rescore
  22. 2026-08-12 23:05 UTCEG score recompute
  23. 2026-08-12 23:05 UTCVendor advisory
  24. 2026-08-12 23:05 UTCGHSA enrichment
  25. 2026-08-12 13:51 UTCEPSS rescore
  26. 2026-08-11 13:43 UTCEPSS rescore
  27. 2026-08-11 07:46 UTCEG score recompute
  28. 2026-08-11 07:46 UTCVendor advisory
  29. 2026-08-11 07:46 UTCGHSA enrichment
  30. 2026-08-11 00:00 UTCEPSS rescore
  31. 2026-08-10 07:40 UTCEG score recompute
  32. 2026-08-10 07:40 UTCVendor advisory
  33. 2026-08-10 07:40 UTCGHSA enrichment
  34. 2026-08-09 13:46 UTCEPSS rescore
  35. 2026-08-09 07:33 UTCEG score recompute
  36. 2026-08-09 07:33 UTCVendor advisory
  37. 2026-08-09 07:33 UTCGHSA enrichment
  38. 2026-08-08 16:37 UTCEPSS rescore
  39. 2026-08-07 18:22 UTCEG score recompute
  40. 2026-08-07 18:22 UTCVendor advisory
  41. 2026-08-07 18:22 UTCGHSA enrichment
  42. 2026-08-06 13:46 UTCEPSS rescore
  43. 2026-08-06 02:04 UTCEG score recompute
  44. 2026-08-06 02:04 UTCVendor advisory
  45. 2026-08-06 02:04 UTCGHSA enrichment
  46. 2026-08-05 19:17 UTCEPSS rescore
  47. 2026-08-04 15:10 UTCEPSS rescore
  48. 2026-08-04 10:38 UTCEPSS rescore
  49. 2026-08-04 01:23 UTCVendor advisory
  50. 2026-08-04 01:23 UTCGHSA enrichment
  51. 2026-08-02 17:39 UTCEG score recompute
  52. 2026-08-02 17:39 UTCVendor advisory
  53. 2026-08-02 17:39 UTCGHSA enrichment
  54. 2026-08-02 02:27 UTCEPSS rescore
  55. 2026-08-01 04:16 UTCEPSS rescore
  56. 2026-07-30 16:28 UTCEPSS rescore
  57. 2026-07-30 01:30 UTCEPSS rescore
  58. 2026-07-27 14:13 UTCEPSS rescore
  59. 2026-07-27 12:52 UTCEG score recompute
  60. 2026-07-27 12:52 UTCVendor advisory
  61. 2026-07-27 12:52 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-3783?
CVE-2026-3783 is a medium vulnerability published on March 11, 2026. 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…
When was CVE-2026-3783 disclosed?
CVE-2026-3783 was first published in the National Vulnerability Database on March 11, 2026, with the most recent update on September 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-3783 actively exploited?
CVE-2026-3783 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 61.2% of all scored CVEs.
What is the CVSS score of CVE-2026-3783?
CVE-2026-3783 has a CVSS v3.1 base score of 5.3 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-3783?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-3783, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-3783

Explore →

Is Your Infrastructure Affected by CVE-2026-3783?

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