CVE-2019-15691
CVSS v3
7.2
HIGH
EPSS Score
4.7 %
exploit probability, as of 2026-10-19
CISA KEV
No
known exploited
Exploitation
—
SSVC status
Get an alert for each new CVE published for tigervnc.
Affected and fixed versions
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Vendor advisories
tigervnc: Stack use-after-return due to incorrect usage of stack memory in ZRLEDecoder
tigervnc as a component of Red Hat Enterprise Linux 6 · tigervnc-server as a component of Red Hat Enterprise Linux 6 · tigervnc-server-applet as a component of Red Hat Enterprise Linux 6
Red Hat Security Advisory: tigervnc security and bug fix update
Red Hat Security Advisory: tigervnc security update
Description
TigerVNC version prior to 1.10.1 is vulnerable to stack use-after-return, which occurs due to incorrect usage of stack memory in ZRLEDecoder. If decoding routine would throw an exception, ZRLEDecoder may try to access stack variable, which has been already freed during the process of stack unwinding. Exploitation of this vulnerability could potentially result into remote code execution. This attack appear to be exploitable via network connectivity.
Technical details
- Published
- 2019-12-26
Frequently asked questions
What is CVE-2019-15691?
Is CVE-2019-15691 actively exploited?
What is the CVSS score for CVE-2019-15691?
Running tigervnc? Hear about its next vulnerability
CVE Watch matches each new CVE to the vendors and products you list (vendor and product, not the version) and puts it in your alerts with its KEV and EPSS status.
Already have an account? Open CVE WatchNo credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? CVE Watch alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.