Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-6253proxy credentials leak over redirect-to proxy

Description

curl might erroneously pass on credentials for a first proxy to a second proxy. This can happen when the following conditions are true: 1. curl is setup to use specific different proxies for different URL schemes 2. the first proxy needs credentials 3. the second proxy uses no credentials 4. while using the first proxy (using say `http://`), curl is asked to follow a redirect to a URL using another scheme (say `https://`), accessed using a second, different, proxy

Public exploit

An exploit or proof of concept is public: anyone can try it against an unpatched system. A reference of the record is tagged as an exploit. CISA's SSVC rates its exploitation: a proof of concept is public.

Show the exploits1

References tagged exploit1 reference

Timeline

  1. ID reserved

    By curl

  2. · 30 days later

    Published

  3. · 4 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-6253, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1Medium5.9CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.1Medium5.9CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.72% · top 46% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: poc · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.9.

Affected products

  • curl · curl

    • affected 7.14.1 – < 8.14.2
    • affected 8.15.0 – < 8.16.1
    • affected 8.17.0 – < 8.20.0
  • curl · curl

    • affected 3b60bb725913ce7339aefef0a14b12df4c24db60 – < 188c2f166a20fa97c2325b2da7d0e5cecc13725f
  • curl · curl

    • affected 8.19.0
    • affected 8.18.0
    • affected 8.17.0
    • affected 8.16.0
    • affected 8.15.0
    • affected 8.14.1
    • affected 8.14.0
    • affected 8.13.0
    • affected 8.12.1
    • affected 8.12.0
    • affected 8.11.1
    • affected 8.11.0
    • affected 8.10.1
    • affected 8.10.0
    • affected 8.9.1
    • affected 8.9.0
    • affected 8.8.0
    • affected 8.7.1
    • affected 8.7.0
    • affected 8.6.0
    • affected 8.5.0
    • affected 8.4.0
    • affected 8.3.0
    • affected 8.2.1
    • affected 8.2.0
    • affected 8.1.2
    • affected 8.1.1
    • affected 8.1.0
    • affected 8.0.1
    • affected 8.0.0
    • affected 7.88.1
    • affected 7.88.0
    • affected 7.87.0
    • affected 7.86.0
    • affected 7.85.0
    • affected 7.84.0
    • affected 7.83.1
    • affected 7.83.0
    • affected 7.82.0
    • affected 7.81.0
    • and 117 more

References

References4

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-6253 badge
[![CVE-2026-6253](https://cveledger.app/badge/CVE-2026-6253.svg)](https://cveledger.app/cve/CVE-2026-6253)

Record last updated .