Vulnerability Database · PyPI · Package report

restkit: vulnerability history, versions and safety

restkit is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 54 releases, from Aug 2017 to May 2022. 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 M1 U1
i
2 with no fix published

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

See the unfixed vulnerabilities →
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.

Vulert verdict on restkit 4.2.2 i

Updated on 23 Oct 2026

Careful: 4.2.2 has 2 known vulnerabilities, and 2 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Little adoption
  • Community Not enough data

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 4.2.2 — affected i
  • Vulnerabilities on record 2 over 4 years · 0 in the last year i
  • Latest disclosure 17 May 2022 i
  • Highest CVSS 5.9 i
  • With no published fix 2 i
  • Depended on by 4 packages i
  • Last release 157 months ago i
  • Licence MIT 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 restkit, 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
4.2.2 30 Aug 2013 M1 U1 MIT No Details →
4.2.1 09 Feb 2013 M1 U1 MIT No Details →
4.2.0 01 Aug 2012 M1 U1 MIT No Details →
4.1.5 28 Jul 2012 M1 U1 MIT No Details →
4.1.4 24 Jul 2012 M1 U1 MIT No Details →
4.1.3 06 Jun 2012 M1 U1 MIT No Details →
4.1.2 06 Feb 2012 M1 U1 non-standard No Details →
4.1.1 31 Jan 2012 M1 U1 non-standard No Details →
4.1.0 31 Jan 2012 M1 U1 non-standard No Details →
4.0.0 26 Jan 2012 M1 U1 non-standard No Details →
3.3.2 30 Sep 2011 M1 U1 non-standard No Details →
3.3.1 19 Sep 2011 M1 U1 non-standard No Details →
3.3.0 20 Jun 2011 M1 U1 non-standard No Details →
3.2.3 05 Apr 2011 M1 U1 non-standard No Details →
3.2.2 05 Apr 2011 M1 U1 non-standard No Details →
3.2.1 22 Mar 2011 M1 U1 non-standard No Details →
3.2.0 19 Feb 2011 M1 U1 non-standard No Details →
3.0.4 08 Feb 2011 M1 U1 non-standard No Details →
3.0.3 07 Feb 2011 M1 U1 non-standard No Details →
3.0.2 03 Feb 2011 M1 U1 non-standard No Details →
3.0.1 03 Feb 2011 M1 U1 non-standard No Details →
3.0.0 03 Feb 2011 M1 U1 non-standard No Details →
2.3.3 17 Dec 2010 M1 U1 non-standard No Details →
2.3.2 15 Dec 2010 M1 U1 non-standard No Details →
2.3.1 25 Nov 2010 M1 U1 non-standard No Details →
2.3.0 25 Nov 2010 M1 U1 non-standard No Details →
2.2.4 19 Nov 2010 M1 U1 non-standard No Details →
2.2.3 03 Nov 2010 M1 U1 non-standard No Details →
2.2.2 16 Oct 2010 M1 U1 non-standard No Details →
2.2.1 18 Sep 2010 M1 U1 non-standard No Details →
2.2.0 14 Sep 2010 M1 U1 non-standard No Details →
2.1.7 07 Sep 2010 M1 U1 non-standard No Details →
2.1.6 02 Sep 2010 M1 U1 non-standard No Details →
2.1.5 14 Aug 2010 M1 U1 non-standard No Details →
2.1.4 13 Aug 2010 M1 U1 non-standard No Details →
2.1.3 11 Aug 2010 M1 U1 non-standard No Details →
2.1.2 10 Aug 2010 M1 U1 non-standard No Details →
2.1.1 05 Aug 2010 M1 U1 non-standard No Details →
2.1.0 24 Jul 2010 M1 U1 non-standard No Details →
2.0.5 20 Jul 2010 M1 U1 non-standard No Details →
2.0.4 15 Jul 2010 M1 U1 non-standard No Details →
2.0.2 07 Jul 2010 M1 U1 non-standard No Details →
2.0.1 05 Jul 2010 M1 U1 non-standard No Details →
2.0.0 27 Jun 2010 M1 U1 non-standard No Details →
1.3.1 09 Apr 2010 M1 U1 non-standard No Details →
1.3.0 02 Apr 2010 M1 U1 non-standard No Details →
1.2.1 08 Mar 2010 M1 U1 non-standard No Details →
1.2.0 07 Mar 2010 M1 U1 non-standard No Details →
1.1.3 04 Mar 2010 M1 U1 non-standard No Details →
1.1.2 02 Mar 2010 M1 U1 non-standard No Details →
1.1.1 01 Mar 2010 M1 U1 non-standard No Details →
1.1.0 01 Mar 2010 M1 U1 non-standard No Details →
1.0.0 28 Feb 2010 M1 U1 non-standard No Details →
2.1.4.win32-py2.7 — M1 U1 — No Details →

All 54 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
  • 2022 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 restkit

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →

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 restkit

Is restkit safe to use?

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

What is restkit's Vulert package health score?

Vulert scores restkit 60/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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of restkit affected?

Yes. 4.2.2, the version you would install today, has 2 known vulnerabilities, and 2 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of restkit should I use?

4.2.2 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 restkit have?

2 vulnerabilities are recorded for restkit in the PyPI ecosystem: 0 critical, 0 high, 1 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 restkit vulnerabilities disclosed?

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

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