VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

libvncserver: vulnerability history, versions and safety

libvncserver is a package in the Debian ecosystem. Vulert records 81 vulnerabilities for it across 12 releases, from Jul 2006 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
81 vulnerabilities recorded U81
i
5 with no fix published

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

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

Most recent disclosure 15 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all libvncserver vulnerabilities

Vulert verdict on libvncserver i

Updated on 23 Oct 2026

Careful: 5 of the 81 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 81 vulnerabilities on record across 19 years, 4 in the last year.

What to do: Plan around the 5 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 81 over 19 years · 4 in the last year i
  • Latest disclosure 15 Jun 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 5 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 libvncserver, 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

  • 2006 2
  • 2014 10
  • 2016 2
  • 2018 19
  • 2019 8
  • 2020 32
  • 2022 2
  • 2025 2
  • 2026 4

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

03 Vulnerabilities

Recorded vulnerabilities for libvncserver

The 5 most severe of 81 vulnerabilities recorded for this package

Search all 81 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Heap-Based Buffer Overflow in LibVNCServer Due to Improper WebSocket Frame Decoding 9.8 critical 0.9.12+dfsg-3 30 Jun 2020
Integer Overflow and Heap-Based Buffer Overflow in LibVNCServer (CVE-2019-20788) 9.8 critical 0.9.12+dfsg-9 23 Apr 2020
Heap Out-of-Bound Write Vulnerability in LibVNC - Remote Code Execution Risk 9.8 critical 0.9.11+dfsg-1.2 19 Dec 2018
Critical Heap Out-of-Bound Write Vulnerability in libVNCServer 9.8 critical 0.9.11+dfsg-1.2 19 Dec 2018
Heap Use-After-Free Vulnerability in LibVNCServer: Remote Code Execution Risk 9.8 critical 0.9.11+dfsg-1.2 19 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 libvncserver

Is libvncserver safe to use?

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

How many vulnerabilities does libvncserver have?

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

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

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