VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

requests: vulnerability history, versions and safety

requests is a package in the Debian ecosystem. Vulert records 10 vulnerabilities for it across 12 releases, from Oct 2014 to Mar 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
10 vulnerabilities recorded U10
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
1 in the last 12 months

Most recent disclosure 25 Mar 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all requests vulnerabilities

Vulert verdict on requests i

Updated on 23 Oct 2026

Careful: 2 of the 10 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 10 vulnerabilities on record across 11 years, 1 in the last year.

What to do: Plan around the 2 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 10 over 11 years · 1 in the last year i
  • Latest disclosure 25 Mar 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 2 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for requests, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 12 of 12 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2014 4
  • 2015 2
  • 2018 2
  • 2023 1
  • 2026 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 10 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for requests

The 5 most severe of 10 vulnerabilities recorded for this package

Search all 10 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2018-18074: Requests package sends HTTP Authorization header to an HTTP URI upon receiving a same-hostname HTTPS-to-HTTP redirect 7.5 high 2.20.0-1 09 Oct 2018
CVE-2023-32681: Unintended leak of Proxy-Authorization header in python-requests 6.1 medium No fix published 26 May 2023
Local File Overwrite Vulnerability in Requests Package 4.4 medium No fix published 25 Mar 2026
Remote Password Exposure in Requests Package - CVE-2014-1829 N/A unrated 2.3.0-1 15 Oct 2014
Sensitive Information Exposure in Requests Package - CVE-2014-1830 N/A unrated 2.3.0-1 15 Oct 2014

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About requests

Is requests safe to use?

Vulert records 10 vulnerabilities for requests in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 10 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does requests have?

10 vulnerabilities are recorded for requests in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 10 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new requests vulnerabilities disclosed?

1 vulnerability was recorded for requests in the last 12 months, and the oldest entry in this database dates to 15 Oct 2014. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of requests are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor requests for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the requests version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.