VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

requests-kerberos: vulnerability history, versions and safety

requests-kerberos is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 4 releases, from Dec 2019 to Mar 2020. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded C1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all requests-kerberos vulnerabilities

Vulert verdict on requests-kerberos 0.15.0 i

Updated on 23 Oct 2026

Good news: 0.15.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 59/100
  • Security Some issues to review
  • Maintenance Maintaining
  • Popularity Niche
  • Community Quiet

What to do: Stay on 0.15.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 0.15.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 0.15.0 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 10 Mar 2020 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 82 packages i
  • Stars 305 i
  • OpenSSF scorecard 2/10 i
  • Last release 28 months ago i
  • Licence non-standard i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

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 tracks for requests-kerberos, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
0.15.0 03 Jun 2024 none non-standard — Details →
0.14.0 05 Dec 2021 none non-standard — Details →
0.13.0 03 Nov 2021 none non-standard — Details →
0.13.0rc1 30 Oct 2021 none non-standard — Details →
0.12.0 20 Dec 2017 none — — Details →
0.12.0b1 09 Dec 2017 none — — Details →
0.11.0 02 Nov 2016 none — — Details →
0.10.0 18 May 2016 none — — Details →
0.9.0 06 May 2016 none — — Details →
0.8.0 07 Jan 2016 none — — Details →
0.7.0 04 May 2015 none — — Details →
0.6.1 15 Nov 2014 none — — Details →
0.6.0 04 Nov 2014 none — — Details →
0.5.0 21 May 2014 C1 U1 — Yes Details →
0.4.0 25 Oct 2013 C1 U1 — Yes Details →
0.3.0 02 Jun 2013 C1 U1 — Yes Details →
0.2.0 26 Mar 2013 C1 U1 — Yes Details →

All 17 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 1
  • 2020 1

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

03 Vulnerabilities

Recorded vulnerabilities for requests-kerberos

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2014-8650: Improper Authentication in requests-kerberos 9.8 critical 0.6 10 Mar 2020
CVE-2014-8650: python-requests-Kerberos through 0.5 Mutual Authentication Handling Vulnerability N/A unrated 0.6 15 Dec 2019

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-kerberos

Is requests-kerberos safe to use?

Vulert records 2 vulnerabilities for requests-kerberos in PyPI: 1 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is requests-kerberos's Vulert package health score?

Vulert scores requests-kerberos 59/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of requests-kerberos affected?

No. 0.15.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of requests-kerberos should I use?

0.15.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does requests-kerberos have?

2 vulnerabilities are recorded for requests-kerberos in the PyPI ecosystem: 1 critical, 0 high, 0 medium and 0 low, plus 1 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-kerberos vulnerabilities disclosed?

0 vulnerabilities were recorded for requests-kerberos in the last 12 months, and the oldest entry in this database dates to 15 Dec 2019. 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-kerberos 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-kerberos for upcoming vulnerabilities?

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