VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

libxcursor: vulnerability history, versions and safety

libxcursor is a package in the Debian ecosystem. Vulert records 5 vulnerabilities for it across 3 affected ranges, from Jun 2013 to Aug 2018. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded U5
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 libxcursor vulnerabilities

Vulert verdict on libxcursor i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 01 Aug 2018. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 5 vulnerabilities on record across 5 years, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 5 over 5 years · 0 in the last year i
  • Latest disclosure 01 Aug 2018 i
  • Highest CVSS 9.8 i
  • With no published fix 0 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
up to 1:1.1.15-1 (exclusive) 2
up to 1:1.1.14-3.1 (exclusive) 1
up to 1:1.1.13-1+deb7u1 (exclusive) 2

02 Disclosure history

How often vulnerabilities are recorded

  • 2013 2
  • 2017 1
  • 2018 2

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

03 Vulnerabilities

Recorded vulnerabilities for libxcursor

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Heap Overflow Vulnerability in libXcursor 9.8 critical 1:1.1.15-1 01 Aug 2018
Integer Overflow Vulnerability in libXcursor: Memory Allocation Flaw N/A unrated 1:1.1.13-1+deb7u1 15 Jun 2013
Integer Overflow Vulnerability in libxcursor Package N/A unrated 1:1.1.13-1+deb7u1 15 Jun 2013
Heap Overflow Vulnerability in libxcursor: Denial of Service Risk N/A unrated 1:1.1.15-1 01 Aug 2018
Integer Overflow Vulnerability in libXcursor and Wayland: CVE-2017-16612 N/A unrated 1:1.1.14-3.1 01 Dec 2017

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 libxcursor

Is libxcursor safe to use?

Vulert records 5 vulnerabilities for libxcursor in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 5 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.

How many vulnerabilities does libxcursor have?

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

0 vulnerabilities were recorded for libxcursor in the last 12 months, and the oldest entry in this database dates to 15 Jun 2013. 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 libxcursor 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 libxcursor for upcoming vulnerabilities?

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