VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

python-cjson: vulnerability history, versions and safety

python-cjson is a package in the PyPI ecosystem. Vulert records 4 vulnerabilities for it across 6 releases, from Jul 2010 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
4 vulnerabilities recorded M2 U2
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 python-cjson vulnerabilities

Vulert verdict on python-cjson 1.2.2 i

Updated on 23 Oct 2026

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

Package health score 48/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Little adoption
  • Community Inactive

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

  • Current release 1.2.2 — unaffected i
  • Vulnerabilities on record 4 over 11 years · 0 in the last year i
  • Latest disclosure 17 May 2022 i
  • Highest CVSS 6.9 i
  • With no published fix 0 i
  • Depended on by 2 packages i
  • Stars 44 i
  • OpenSSF scorecard 1/10 i
  • Last release 79 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 python-cjson, 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.2 20 Mar 2020 none non-standard — Details →
1.2.1 28 Feb 2017 none non-standard — Details →
1.2.0 28 Feb 2017 none non-standard — Details →
1.1.0 24 Jun 2014 none non-standard — Details →
1.0.5 24 Aug 2007 M2 U2 non-standard Yes Details →
1.0.4 25 Jul 2007 M2 U2 non-standard Yes Details →
1.0.3 27 Jan 2007 M2 U2 non-standard Yes Details →
1.0.2 20 Dec 2006 M2 U2 non-standard Yes Details →
1.0.1 20 Dec 2006 M2 U2 non-standard Yes Details →
1.0.0 19 Dec 2006 M2 U2 non-standard Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2010 2
  • 2021 1
  • 2022 1

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

03 Vulnerabilities

Recorded vulnerabilities for python-cjson

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2010-1666: Buffer Overflow in python-cjson 6.9 medium 1.0.5.1 17 May 2022
CVE-2009-4924: Cross-site Scripting in python-cjson 6.1 medium 1.1.0 06 Dec 2021
CVE-2009-4924: python-cjson Remote Cross-Site Scripting (XSS) Vulnerability N/A unrated 1.1.0 02 Jul 2010
CVE-2010-1666: Buffer Overflow in python-cjson N/A unrated 1.1.0 02 Jul 2010

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 python-cjson

Is python-cjson safe to use?

Vulert records 4 vulnerabilities for python-cjson in PyPI: 0 critical, 0 high, 2 medium and 0 low, plus 2 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 python-cjson's Vulert package health score?

Vulert scores python-cjson 48/100, which reads as risky. 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 python-cjson affected?

No. 1.2.2, 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 python-cjson should I use?

1.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 python-cjson have?

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

0 vulnerabilities were recorded for python-cjson in the last 12 months, and the oldest entry in this database dates to 02 Jul 2010. 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 python-cjson 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 python-cjson for upcoming vulnerabilities?

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