Vulnerabilities

Vulnerability · CVE-2026-3783

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 cir

Published Mar 11, 2026 · catalog updated Oct 18, 2026 · When an OAuth2 bearer

Check if you run it

No confirmed exploitation is on record for CVE-2026-3783. EPSS is 0.53%. Act only if a listed version of When an OAuth2 bearer is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (When an OAuth2 bearer).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium5.3
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.53%
Remediation
Advisory link
Affected products
Alpine:v3.21 curl · Alpine:v3.22 curl · Alpine:v3.23 curl · Alpine:v3.24 curl · cpe haxx/curl

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 or keywords, curl would pass on the bearer token set for the first host also to the second one.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Alpine:v3.21 curl7.33.0 → 8.14.1-r3
  • Alpine:v3.22 curl7.33.0 → 8.14.1-r4
  • Alpine:v3.23 curl7.33.0 → 8.19.0-r0
  • Alpine:v3.24 curl7.33.0 → 8.19.0-r0
  • cpe haxx/curlversion unspecified

How to fix CVE-2026-3783

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-3783. EPSS is 0.53%. Act only if a listed version of When an OAuth2 bearer is installed.

Which versions are affected?

Compare what you have installed with 7.33.0 → 8.14.1-r3, 7.33.0 → 8.14.1-r4, 7.33.0 → 8.19.0-r0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-522: Insufficiently Protected Credentials. EPSS 0.53%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Mar 11, 2026 · NIST NVD

    Detected

    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 or keywords, curl would pass on the bearer token set for the first host also to the second o

  2. Sep 15, 2026 · NIST NVD

    Updated

    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 or keywords, curl would pass on the bearer token set for the first host also to the second o

  3. Oct 18, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    curl fixed in 8.14.1-r3; curl fixed in 8.14.1-r4; curl fixed in 8.19.0-r0; curl fixed in 8.19.0-r0

  4. Oct 18, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    curl fixed in 8.14.1-r3

  5. Oct 18, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    curl fixed in 8.14.1-r4

  6. Oct 18, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    curl fixed in 8.19.0-r0

  7. Oct 18, 2026 · OpenSSF OSV / OSV Scanner

    Updated

    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 or keywords, curl would pass on the bearer token set for the first host also to the second o

Sources

  • CVE.orgVulnerability recordCVE-2026-3783

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-3783

    30-day exploitation probability 0.5%

    first.org
  • NIST NVDVulnerability recordCVE-2026-3783

    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 .ne

    nvd.nist.gov
  • OpenSSF OSV / OSV ScannerPackage advisoryALPINE-CVE-2026-3783
    osv.dev
  • Trivy Vulnerability DBPackage advisoryALPINE-CVE-2026-3783

    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 .net

    osv.dev

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.