VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

pykerberos: vulnerability history, versions and safety

pykerberos is a package in the PyPI ecosystem. Vulert records 1 vulnerability for it across 3 releases, first recorded in Aug 2017. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded 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 pykerberos vulnerabilities

Vulert verdict on pykerberos 1.2.4 i

Updated on 23 Oct 2026

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

Package health score 57/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Little adoption
  • Community Quiet

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

  • Current release 1.2.4 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 25 Aug 2017 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 22 packages i
  • Stars 23 i
  • OpenSSF scorecard 2/10 i
  • Last release 55 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 pykerberos, 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
1.2.4 09 Mar 2022 none non-standard — Details →
1.2.3.dev0 27 Feb 2020 none non-standard — Details →
1.2.1 20 Dec 2017 none non-standard — Details →
1.2.1b1 09 Dec 2017 none non-standard — Details →
1.1.14 26 Jan 2017 none non-standard — Details →
1.1.13 03 Jun 2016 none non-standard — Details →
1.1.12 01 Jun 2016 none non-standard — Details →
1.1.11 27 May 2016 none non-standard — Details →
1.1.10 07 Feb 2016 none non-standard — Details →
1.1.9 17 Dec 2015 none non-standard — Details →
1.1.8 24 Aug 2015 none non-standard — Details →
1.1.6 17 May 2015 none non-standard — Details →
1.1.5 25 Mar 2014 U1 non-standard Yes Details →
1.1.4 12 Feb 2014 U1 non-standard Yes Details →
1.1.3 12 Feb 2014 U1 non-standard Yes Details →
1.1.7.post1 — none non-standard — Details →
1.2.2.dev0-py3.5-macosx-10.12-x86_64 — none — — 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

  • 2017 1

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

03 Vulnerabilities

Recorded vulnerabilities for pykerberos

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2015-3206: Vulnerability in pykerberos Package N/A unrated 1.1.6 25 Aug 2017

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 pykerberos

Is pykerberos safe to use?

Vulert records 1 vulnerabilities for pykerberos in PyPI: 0 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 pykerberos's Vulert package health score?

Vulert scores pykerberos 57/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 pykerberos affected?

No. 1.2.4, 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 pykerberos should I use?

1.2.4 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 pykerberos have?

1 vulnerability is recorded for pykerberos in the PyPI ecosystem: 0 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 pykerberos vulnerabilities disclosed?

0 vulnerabilities were recorded for pykerberos in the last 12 months, and the oldest entry in this database dates to 25 Aug 2017. 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 pykerberos 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 pykerberos for upcoming vulnerabilities?

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