VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

libcaca: vulnerability history, versions and safety

libcaca is a package in the Debian ecosystem. Vulert records 22 vulnerabilities for it across 12 releases, from Dec 2018 to May 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
22 vulnerabilities recorded U22
i
3 with no fix published

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

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

Most recent disclosure 11 May 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all libcaca vulnerabilities

Vulert verdict on libcaca i

Updated on 23 Oct 2026

Careful: 3 of the 22 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 22 vulnerabilities on record across 7 years, 1 in the last year.

What to do: Plan around the 3 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 22 over 7 years · 1 in the last year i
  • Latest disclosure 11 May 2026 i
  • Highest CVSS 8.8 i
  • With no published fix 3 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

Every version Vulert holds for libcaca, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 12 of 12 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 12
  • 2021 6
  • 2022 2
  • 2025 1
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for libcaca

The 5 most severe of 22 vulnerabilities recorded for this package

Search all 22 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Illegal WRITE Memory Access in libcaca 0.99.beta19 8.8 high 0.99.beta19-2.1 28 Dec 2018
Illegal WRITE Memory Access in libcaca 8.8 high 0.99.beta19-2.1 28 Dec 2018
Illegal WRITE Memory Access in libcaca 8.8 high 0.99.beta19-2.1 28 Dec 2018
Illegal READ Memory Access in libcaca 0.99.beta19 8.1 high 0.99.beta19-2.1 28 Dec 2018
Memory Read Access Vulnerability in libcaca 8.1 high 0.99.beta19-2.1 28 Dec 2018

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 libcaca

Is libcaca safe to use?

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

How many vulnerabilities does libcaca have?

22 vulnerabilities are recorded for libcaca in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 22 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 libcaca vulnerabilities disclosed?

1 vulnerability was recorded for libcaca in the last 12 months, and the oldest entry in this database dates to 28 Dec 2018. 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 libcaca 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 libcaca for upcoming vulnerabilities?

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