VulertSecurity VulertSecurity

Vulnerability Database · OSS-Fuzz · Package report

libical: vulnerability history, versions and safety

libical is a package in the OSS-Fuzz ecosystem. Vulert records 15 vulnerabilities for it across 11 affected ranges, from Jul 2020 to Apr 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
15 vulnerabilities recorded H5 M7 U3
i
2 with no fix published

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

See the unfixed vulnerabilities →
i
7 in the last 12 months

Most recent disclosure 25 Apr 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all libical vulnerabilities

Vulert verdict on libical i

Updated on 23 Oct 2026

Careful: 2 of the 15 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 15 vulnerabilities on record across 5 years, 7 in the last year.

What to do: Plan around the 2 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 15 over 5 years · 7 in the last year i
  • Latest disclosure 25 Apr 2026 i
  • Highest CVSS n/a i
  • With no published fix 2 i

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

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

i
Affected range Vulnerabilities
from 771f633543950540e518ff8c1f55253722221695 up to 645068e8371c7e0b5f0f75c48cbf3e04ccca49ba (exclusive) 3
from 1d7bd24caf33d607c0863dceb83ccb5cfd54fb91 up to 130581f5cdb6501da8533b7bd3cae92eb01ea18a (exclusive) 1
from f8cb7b4349809e51bad3902d130804d31ede3116 up to 899c2f3a4325a4093b02e9c913208a6a2299c8e5 (exclusive) 1
from c63cb1951b339aef71265bc92d23d211d0ac554a up to 6b7b9c2612dc5c8ee1f7d2604c417666e883a2e6 (exclusive) 1
from f8cb7b4349809e51bad3902d130804d31ede3116 up to 0d3735426835aff0bd8151a0203e0720b157315f (exclusive) 3
from 00fc43fd2faaa5a3d0a667dbb56bd35ba758892d up to 0d3735426835aff0bd8151a0203e0720b157315f (exclusive) 1
from a5977add5b862817f9f136fef6b1c6001c6710de up to a38954a0a035f3a049af7e1150df4b90655810d5 (exclusive) 1
from b0aa3088b8b7aeafba3624c957e8eea3ad72b7a7 up to d86a86dbcddba0414f0dea13c3357f1c38826cb2 (exclusive) 1
from f8cb7b4349809e51bad3902d130804d31ede3116 up to e6c4d276a1df6c73bd2bec2c53dd98e367126375 (exclusive) 1
from 2026582a94915dc3988b40ab222a4d975fd0f10c onwards, no fix published yet 1
from a5977add5b862817f9f136fef6b1c6001c6710de onwards, no fix published yet 1

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 3
  • 2022 1
  • 2024 1
  • 2025 4
  • 2026 6

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

03 Vulnerabilities

Recorded vulnerabilities for libical

The 5 most severe of 15 vulnerabilities recorded for this package

Search all 15 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Heap-Use-After-Free Vulnerability in libical: Critical Security Flaw N/A high 0d3735426835aff0bd8151a0203e0720b157315f 21 Feb 2026
Heap Buffer Overflow Vulnerability in libical: Critical Security Flaw Detected N/A high 130581f5cdb6501da8533b7bd3cae92eb01ea18a 10 Nov 2025
Segmentation Fault in libical: Vulnerability in icalarray_append Function N/A unrated e6c4d276a1df6c73bd2bec2c53dd98e367126375 06 Feb 2026
Uninitialized Value Vulnerability in libical: Use-of-Uninitialized-Value in vcardstructured_free N/A medium 0d3735426835aff0bd8151a0203e0720b157315f 05 Feb 2026
Critical UNKNOWN READ Vulnerability in libical: strncasecmp Function N/A medium 0d3735426835aff0bd8151a0203e0720b157315f 26 Feb 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 libical

Is libical safe to use?

Vulert records 15 vulnerabilities for libical in OSS-Fuzz: 0 critical, 5 high, 7 medium and 0 low, plus 3 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does libical have?

15 vulnerabilities are recorded for libical in the OSS-Fuzz ecosystem: 0 critical, 5 high, 7 medium and 0 low, plus 3 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 libical vulnerabilities disclosed?

7 vulnerabilities were recorded for libical in the last 12 months, and the oldest entry in this database dates to 01 Jul 2020. 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 libical 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 libical for upcoming vulnerabilities?

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