VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

icalendar: vulnerability history, versions and safety

icalendar is a package in the RubyGems ecosystem. Vulert records 1 vulnerability for it across 30 releases, first recorded in Mar 2026. 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 M1
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 24 Mar 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all icalendar vulnerabilities

Vulert verdict on icalendar 2.13.0 i

Updated on 23 Oct 2026

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

Package health score 96/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Not enough data
  • Community Not enough data

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

  • Current release 2.13.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 24 Mar 2026 i
  • Highest CVSS 4.3 i
  • With no published fix 0 i
  • Last release this month i
  • Licence BSD-2-Clause i

Version list, release dates, licence and dependants published by RubyGems, refreshed 22 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 icalendar, 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
2.13.0 11 Oct 2026 none BSD-2-Clause — Details →
2.12.5 25 Sep 2026 none BSD-2-Clause — Details →
2.12.4 31 Jul 2026 none BSD-2-Clause — Details →
2.12.3 13 May 2026 none BSD-2-Clause — Details →
2.12.2 21 Mar 2026 none BSD-2-Clause — Details →
2.12.1 19 Oct 2025 M1 BSD-2-Clause Yes Details →
2.12.0 26 Sep 2025 M1 BSD-2-Clause Yes Details →
2.11.2 21 Jun 2025 M1 BSD-2-Clause Yes Details →
2.11.1 06 Jun 2025 M1 BSD-2-Clause Yes Details →
2.11.0 12 Apr 2025 M1 BSD-2-Clause Yes Details →
2.10.3 21 Sep 2024 M1 BSD-2-Clause Yes Details →
2.10.2 21 Jul 2024 M1 BSD-2-Clause Yes Details →
2.10.1 01 Dec 2023 M1 BSD-2-Clause Yes Details →
2.10.0 01 Nov 2023 M1 BSD-2-Clause Yes Details →
2.9.0 11 Aug 2023 M1 BSD-2-Clause Yes Details →
2.8.0 11 Jul 2022 M1 BSD-2-Clause Yes Details →
2.7.1 15 Mar 2021 M1 — Yes Details →
2.7.0 12 Sep 2020 M1 — Yes Details →
2.6.1 07 Dec 2019 M1 — Yes Details →
2.6.0 27 Nov 2019 M1 — Yes Details →
2.5.3 05 Mar 2019 M1 — Yes Details →
2.5.2 08 Dec 2018 M1 — Yes Details →
2.5.1 30 Oct 2018 M1 — Yes Details →
2.5.0 10 Sep 2018 M1 — Yes Details →
2.4.1 04 Sep 2016 M1 — Yes Details →
2.4.0 05 Jul 2016 M1 — Yes Details →
2.3.0 26 Apr 2015 M1 — Yes Details →
2.2.2 27 Dec 2014 M1 — Yes Details →
2.2.1 04 Dec 2014 M1 — Yes Details →
2.2.0 24 Sep 2014 M1 — Yes Details →
2.1.2 10 Sep 2014 M1 — Yes Details →
2.1.1 24 Jul 2014 M1 — Yes Details →
2.1.0 17 Jun 2014 M1 — Yes Details →
2.0.1 27 Apr 2014 M1 — Yes Details →
1.5.4 27 Apr 2014 none — — Details →
2.0.0 23 Apr 2014 M1 — Yes Details →
1.5.3 20 Apr 2014 none — — Details →
2.0.0.beta.2 11 Apr 2014 none — — Details →
2.0.0.beta.1 30 Mar 2014 none — — Details →
1.5.2 22 Mar 2014 none — — Details →
1.5.1 28 Feb 2014 none — — Details →
1.5.0 07 Dec 2013 none — — Details →
1.4.5 14 Nov 2013 none — — Details →
1.4.4 06 Nov 2013 none — — Details →
1.4.3 18 Sep 2013 none — — Details →
1.4.2 11 Sep 2013 none — — Details →
1.4.1 26 Jun 2013 none — — Details →
1.4.0 22 May 2013 none — — Details →
1.3.0 01 Apr 2013 none — — Details →
1.2.4 30 Mar 2013 none — — Details →
1.2.3 09 Mar 2013 none — — Details →
1.2.2 16 Feb 2013 none — — Details →
1.2.1 21 Nov 2012 none — — Details →
1.2.0 31 Aug 2012 none — — Details →
1.2 31 Aug 2012 none — — Details →
1.1.6 10 Mar 2011 none — — Details →
1.1.5 21 Jun 2010 none — — Details →
1.1.4 23 Apr 2010 none — — Details →
1.1.3 15 Mar 2010 none — — Details →
1.1.2 10 Mar 2010 none — — Details →
1.1.1 06 Mar 2010 none — — Details →
0.95 25 Jul 2009 none — — Details →
0.96.1 25 Jul 2009 none — — Details →
0.96.2 25 Jul 2009 none — — Details →
0.96.3 25 Jul 2009 none — — Details →
0.96.4 25 Jul 2009 none — — Details →
0.96 25 Jul 2009 none — — Details →
0.97 25 Jul 2009 none — — Details →
0.98 25 Jul 2009 none — — Details →
1.0 25 Jul 2009 none — — Details →
1.0.1 25 Jul 2009 none — — Details →
1.0.2 25 Jul 2009 none — — Details →
1.1.0 25 Jul 2009 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for icalendar

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-33635: iCalendar ICS Injection via Unsanitized URI Property Values 4.3 medium 2.12.2 24 Mar 2026

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 icalendar

Is icalendar safe to use?

Vulert records 1 vulnerabilities for icalendar in RubyGems: 0 critical, 0 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is icalendar's Vulert package health score?

Vulert scores icalendar 96/100, which reads as healthy. 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 icalendar affected?

No. 2.13.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 icalendar should I use?

2.13.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 icalendar have?

1 vulnerability is recorded for icalendar in the RubyGems ecosystem: 0 critical, 0 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new icalendar vulnerabilities disclosed?

1 vulnerability was recorded for icalendar in the last 12 months, and the oldest entry in this database dates to 24 Mar 2026. 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 icalendar 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 icalendar for upcoming vulnerabilities?

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