CVE-2018-7226 json
An issue was discovered in vcSetXCutTextProc() in VNConsole.c in LinuxVNC and VNCommand from the LibVNC/vncterm distribution through 0.9.10.
published 2018-02-19 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-18965
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.6%
- EPSS 2.6% chance of exploitation in 30 days, percentile 85%
- public exploits
- 0
- none known
Summary
An issue was discovered in vcSetXCutTextProc() in VNConsole.c in LinuxVNC and VNCommand from the LibVNC/vncterm distribution through 0.9.10. Missing sanitization of the client-specified message length may cause integer overflow or possibly have unspecified other impact via a specially crafted VNC packet.
Patch / fix
- libvncserver Arch Linux 0.9.12-1
arch linux advisories AVG-628
- github.com/LibVNC/vncterm/issues/6 advisory
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2018-7226 updated cvss 5.4
libvncserver: integer overflow in vcSetXCutTextProc in VNConsole.c
-
Red Hat Enterprise Linux 6 libvncserver Red Hat Enterprise Linux 7 libvncservernot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
2.55% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-190 Integer Overflow or Wraparound
References
-
github.com
/LibVNC/vncterm/issues/6
patch, third-party-advisory
-
security.gentoo.org
/glsa/201908-05
vendor-advisory
-
openwall.com
/lists/oss-security/2018/02/18/2
mailing-list
Sources
- CVE List CVE-2018-7226
- NVD CVE-2018-7226
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.