VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

radicale: vulnerability history, versions and safety

radicale is a package in the PyPI ecosystem. Vulert records 8 vulnerabilities for it across 96 releases, from Feb 2016 to Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
8 vulnerabilities recorded C2 H1 M1 U4
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 29 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all radicale vulnerabilities

Vulert verdict on radicale 3.8.3 i

Updated on 23 Oct 2026

Action needed: 3.8.3 has 2 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 75/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 3.8.3 — affected i
  • Vulnerabilities on record 8 over 10 years · 1 in the last year i
  • Latest disclosure 29 Jun 2026 i
  • Highest CVSS 10.0 i
  • With no published fix 0 i
  • Depended on by 17 packages i
  • Stars 5,110 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence GPL-3.0 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 radicale, 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
3.8.3 08 Oct 2026 U2 GPL-3.0 Yes Details →
3.8.2 06 Oct 2026 U2 GPL-3.0 Yes Details →
3.8.1 25 Sep 2026 U2 GPL-3.0 Yes Details →
3.8.0 03 Sep 2026 U2 GPL-3.0 Yes Details →
3.7.8 06 Aug 2026 U2 GPL-3.0 Yes Details →
3.7.7 19 Jul 2026 U2 GPL-3.0 Yes Details →
3.7.6 07 Jul 2026 U2 GPL-3.0 Yes Details →
3.7.5 14 Jun 2026 U2 GPL-3.0 Yes Details →
3.7.4 28 May 2026 U2 GPL-3.0 Yes Details →
3.7.3 14 May 2026 U2 GPL-3.0 Yes Details →
3.7.2 29 Apr 2026 U2 GPL-3.0 Yes Details →
3.7.1 12 Apr 2026 U2 GPL-3.0 Yes Details →
3.7.0 05 Apr 2026 U2 GPL-3.0 Yes Details →
3.6.1 25 Feb 2026 U2 GPL-3.0 Yes Details →
3.6.0 10 Jan 2026 U2 GPL-3.0 Yes Details →
3.5.10 18 Dec 2025 U2 GPL-3.0 Yes Details →
3.5.9 29 Nov 2025 U2 GPL-3.0 Yes Details →
3.5.8 06 Nov 2025 U2 GPL-3.0 Yes Details →
3.5.7 01 Oct 2025 U2 GPL-3.0 Yes Details →
3.5.7.dev0 27 Sep 2025 U2 GPL-3.0 Yes Details →
3.5.6 15 Sep 2025 U2 GPL-3.0 Yes Details →
3.5.5 22 Aug 2025 U2 GPL-3.0 Yes Details →
3.5.4 25 May 2025 U2 GPL-3.0 Yes Details →
3.5.3 11 May 2025 U2 GPL-3.0 Yes Details →
3.5.2 23 Apr 2025 U2 GPL-3.0 Yes Details →
3.5.1 05 Apr 2025 U2 GPL-3.0 Yes Details →
3.5.0 16 Mar 2025 U2 GPL-3.0 Yes Details →
3.4.1 26 Jan 2025 U2 GPL-3.0 Yes Details →
3.4.0 09 Jan 2025 U2 GPL-3.0 Yes Details →
3.3.3 28 Dec 2024 U2 GPL-3.0 Yes Details →
3.3.2 15 Dec 2024 U2 GPL-3.0 Yes Details →
3.3.1 24 Nov 2024 U2 GPL-3.0 Yes Details →
3.3.0 13 Oct 2024 U2 GPL-3.0 Yes Details →
3.2.3 30 Aug 2024 U2 GPL-3.0 Yes Details →
3.2.2 18 Jun 2024 U2 GPL-3.0 Yes Details →
3.0.0.dev0 18 Jun 2024 U2 GPL-3.0 Yes Details →
3.2.1 04 Jun 2024 U2 GPL-3.0 Yes Details →
3.2.0 18 May 2024 U2 GPL-3.0 Yes Details →
3.1.9 18 Mar 2024 U2 GPL-3.0 Yes Details →
3.1.8 14 Jul 2022 U2 GPL-3.0 Yes Details →
3.1.7 20 Apr 2022 U2 GPL-3.0 Yes Details →
3.1.6 18 Apr 2022 U2 GPL-3.0 Yes Details →
3.1.5 08 Feb 2022 U2 GPL-3.0 Yes Details →
3.1.4 01 Feb 2022 U2 GPL-3.0 Yes Details →
3.1.3 26 Jan 2022 U2 GPL-3.0 Yes Details →
3.1.2 21 Jan 2022 U2 GPL-3.0 Yes Details →
3.1.1 19 Jan 2022 U2 GPL-3.0 Yes Details →
3.1.0 26 Dec 2021 U2 GPL-3.0 Yes Details →
3.0.6 14 Sep 2020 U2 GPL-3.0 Yes Details →
3.0.5 31 Aug 2020 U2 GPL-3.0 Yes Details →
3.0.4 18 Aug 2020 U2 GPL-3.0 Yes Details →
3.0.3 06 Jun 2020 U2 GPL-3.0 Yes Details →
3.0.2 24 May 2020 U2 GPL-3.0 Yes Details →
3.0.1 22 May 2020 U2 GPL-3.0 Yes Details →
3.0.0 19 May 2020 U2 GPL-3.0 Yes Details →
2.1.12 19 May 2020 U2 GPL-3.0 Yes Details →
1.1.7 19 May 2020 U2 GPL-3.0 Yes Details →
2.1.11 05 Nov 2018 U2 GPL-3.0 Yes Details →
2.1.10 16 Aug 2018 U2 GPL-3.0 Yes Details →
2.1.9 21 Apr 2018 U2 GPL-3.0 Yes Details →
2.1.8 24 Sep 2017 U2 GPL-3.0 Yes Details →
2.1.7 19 Sep 2017 U2 GPL-3.0 Yes Details →
2.1.6 11 Sep 2017 U2 GPL-3.0 Yes Details →
2.1.5 26 Aug 2017 U2 GPL-3.0 Yes Details →
2.1.4 04 Aug 2017 U2 GPL-3.0 Yes Details →
2.1.3 02 Aug 2017 U2 GPL-3.0 Yes Details →
1.1.6 24 Jul 2017 U2 GPL-3.0 Yes Details →
2.1.2 24 Jul 2017 U2 GPL-3.0 Yes Details →
1.1.5 24 Jul 2017 U2 GPL-3.0 Yes Details →
2.1.1 01 Jul 2017 U2 GPL-3.0 Yes Details →
2.1.0 25 Jun 2017 U2 GPL-3.0 Yes Details →
1.1.4 25 Jun 2017 U2 GPL-3.0 Yes Details →
2.0.0 27 May 2017 U2 GPL-3.0 Yes Details →
1.1.3 27 May 2017 U2 GPL-3.0 Yes Details →
2.0.0rc2 19 Apr 2017 U2 GPL-3.0 Yes Details →
1.1.2 19 Apr 2017 U2 GPL-3.0 Yes Details →
2.0.0rc1 15 Apr 2017 U2 GPL-3.0 Yes Details →
1.1.1 07 Jan 2016 H1 U1 GPL-3.0 Yes Details →
1.1.0 31 Dec 2015 H1 U2 GPL-3.0 Yes Details →
1.0.1 18 Oct 2015 C2 H1 M1 U4 GPL-3.0 Yes Details →
0.10.0 12 Jan 2015 C2 H1 M1 U3 GPL-3.0 Yes Details →
0.9.0 13 Aug 2014 C2 H1 M1 U3 GPL-3.0 Yes Details →
0.9.0b2 28 Jul 2014 C2 H1 M1 U3 GPL-3.0 Yes Details →
0.9.0b1 24 Feb 2014 C2 H1 M1 U3 GPL-3.0 Yes Details →
0.8.0 12 Jul 2013 C2 H1 M1 U3 GPL-3.0 Yes Details →
0.7.1 03 Aug 2012 C2 H1 M1 U4 GPL-3.0 Yes Details →
0.7.0 20 Mar 2012 C2 H1 M1 U3 GPL-3.0 Yes Details →
0.6.4 05 Jan 2012 C2 H1 M1 U4 GPL-3.0 Yes Details →
0.6.3 03 Nov 2011 C2 H1 M1 U4 GPL-3.0 Yes Details →
0.6.2 27 Sep 2011 C2 H1 M1 U4 GPL-3.0 Yes Details →
0.6.1 27 Aug 2011 C2 H1 M1 U4 GPL-3.0 Yes Details →
0.6.0 31 Jul 2011 C2 H1 M1 U3 GPL-3.0 Yes Details →
0.5.0 02 Apr 2011 C2 H1 M1 U3 GPL-3.0 Yes Details →
0.4.0 08 Aug 2010 C2 H1 M1 U3 GPL-3.0 Yes Details →
0.3.0 14 Jun 2010 C2 H1 M1 U3 GPL-3.0 Yes Details →
0.2.0 13 Apr 2010 C2 H1 M1 U3 GPL-3.0 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2016 2
  • 2017 1
  • 2022 4
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for radicale

The 5 most severe of 8 vulnerabilities recorded for this package

Search all 8 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2016-1505: Radicale Directory Traversal Vulnerability 10.0 critical 1.1 17 May 2022
CVE-2015-8747: Radicale Arbitrary File Read or Write 10.0 critical 1.1 17 May 2022
CVE-2016-1505: Radicale Directory Traversal Vulnerability in Windows Filesystem Storage 10.0 critical 1.1 29 Jun 2026
CVE-2017-8342: Radicale Timing Oracles and Simple Brute-Force Attacks 8.1 high 1.1.2 13 May 2022
CVE-2015-8748: Radicale Regex Metacharacters Injection in User Name 5.3 medium 1.1 17 May 2022

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 radicale

Is radicale safe to use?

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

Vulert scores radicale 75/100, which reads as in good shape. 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 radicale affected?

Yes. 3.8.3, the version you would install today, has 2 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of radicale should I use?

3.8.3 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 radicale have?

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

1 vulnerability was recorded for radicale in the last 12 months, and the oldest entry in this database dates to 03 Feb 2016. 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 radicale 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 radicale for upcoming vulnerabilities?

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