In TigerVNC 1.7.1 (SMsgReader.cxx SMsgReader::readClientCutText), by causing an integer overflow, an authenticated client can crash the serv
Noroxi assessment
Priority: Monitor (action score 26/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.4% (FIRST EPSS); higher than 72.3% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: tigervnc (Debian:12) 1.7.0+dfsg-7; fltk (Red Hat:enterprise_linux:7::client) 0:1.3.4-1.el7; fltk-debuginfo (Red Hat:enterprise_linux:7::client) 0:1.3.4-1.el7.
Low priority for now. Upgrade to tigervnc (Debian:12) 1.7.0+dfsg-7; fltk (Red Hat:enterprise_linux:7::client) 0:1.3.4-1.el7; fltk-debuginfo (Red Hat:enterprise_linux:7::client) 0:1.3.4-1.el7 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
In TigerVNC 1.7.1 (SMsgReader.cxx SMsgReader::readClientCutText), by causing an integer overflow, an authenticated client can crash the server.
- Published
- Mar 31, 2017
- Updated
- Jun 16, 2026
- EPSS
- 1.4% · 72th percentile
- CWE
- CWE-190
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.4%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| tigervnc | tigervnc | cpe:2.3:a:tigervnc:tigervnc |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- tigervnc tigervnc1.7.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | tigervnc | before 1.7.0+dfsg-7 | 1.7.0+dfsg-7 |
| Red Hat:enterprise_linux:7::client | fltk | before 0:1.3.4-1.el7 | 0:1.3.4-1.el7 |
| Red Hat:enterprise_linux:7::client | fltk-debuginfo | before 0:1.3.4-1.el7 | 0:1.3.4-1.el7 |
| Red Hat:enterprise_linux:7::client | fltk-devel | before 0:1.3.4-1.el7 | 0:1.3.4-1.el7 |
| Red Hat:enterprise_linux:7::client | fltk-fluid | before 0:1.3.4-1.el7 | 0:1.3.4-1.el7 |
| Red Hat:enterprise_linux:7::client | fltk-static | before 0:1.3.4-1.el7 | 0:1.3.4-1.el7 |
| Red Hat:enterprise_linux:7::client | tigervnc | before 0:1.8.0-1.el7 | 0:1.8.0-1.el7 |
| Red Hat:enterprise_linux:7::client | tigervnc-debuginfo | before 0:1.8.0-1.el7 | 0:1.8.0-1.el7 |
| Red Hat:enterprise_linux:7::client | tigervnc-icons | before 0:1.8.0-1.el7 | 0:1.8.0-1.el7 |
| Red Hat:enterprise_linux:7::client | tigervnc-license | before 0:1.8.0-1.el7 | 0:1.8.0-1.el7 |
| Red Hat:enterprise_linux:7::client | tigervnc-server | before 0:1.8.0-1.el7 | 0:1.8.0-1.el7 |
| Red Hat:enterprise_linux:7::client | tigervnc-server-applet | before 0:1.8.0-1.el7 | 0:1.8.0-1.el7 |
| Red Hat:enterprise_linux:7::client | tigervnc-server-minimal | before 0:1.8.0-1.el7 | 0:1.8.0-1.el7 |
| Red Hat:enterprise_linux:7::client | tigervnc-server-module | before 0:1.8.0-1.el7 | 0:1.8.0-1.el7 |
| SUSE:Linux Enterprise Desktop 12 SP1 | tigervnc | before 1.4.3-24.1 | 1.4.3-24.1 |
| SUSE:Linux Enterprise Desktop 12 SP2 | tigervnc | before 1.6.0-18.11.1 | 1.6.0-18.11.1 |
Same product
tigervnc: all recordsOther highest-scoring records for the same primary product.
- CVE-2014-0011Multiple heap-based buffer overflows in the ZRLE_DECODE function in common/rfb/zrleDecode.h in TigerVNC before 1.3.1, when NDEBUG is enabled40Plan
- CVE-2017-5581Buffer overflow in the ModifiablePixelBuffer::fillRect function in TigerVNC before 1.7.1 allows remote servers to execute arbitrary code via40Plan
- CVE-2014-8241XRegion in TigerVNC allows remote VNC servers to cause a denial of service (NULL pointer dereference) by leveraging failure to check a mallo40Plan
- CVE-2026-34352In TigerVNC before 1.16.2, Image.cxx in x0vncserver allows other users to observe or manipulate the screen contents, or cause an application39Monitor
- CVE-2017-7393In TigerVNC 1.7.1 (VNCSConnectionST.cxx VNCSConnectionST::fence), an authenticated client can cause a double free, leading to denial of serv36Monitor
- CVE-2020-26117In rfb/CSecurityTLS.cxx and rfb/CSecurityTLS.java in TigerVNC before 1.11.0, viewers mishandle TLS certificate exceptions.33Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:tigervnc | 1.7.0+dfsg-7 · Debian:12 | Package registry (OSV) |
| red hat:fltk | 0:1.3.4-1.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:fltk-debuginfo | 0:1.3.4-1.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:fltk-devel | 0:1.3.4-1.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:fltk-fluid | 0:1.3.4-1.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:fltk-static | 0:1.3.4-1.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:tigervnc | 0:1.8.0-1.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:tigervnc-debuginfo | 0:1.8.0-1.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:tigervnc-icons | 0:1.8.0-1.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:tigervnc-license | 0:1.8.0-1.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:tigervnc-server | 0:1.8.0-1.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:tigervnc-server-applet | 0:1.8.0-1.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:tigervnc-server-module | 0:1.8.0-1.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| suse:tigervnc | 1.4.3-24.1 · SUSE:Linux Enterprise Desktop 12 SP1 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-190 · Integer Overflow or WraparoundCVSS vector
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.