CVE-2018-7226: An issue was discovered in vcSetXCutTextProc() in VNConsole.c in LinuxVNC and VNCommand from the LibVNC/vncter

Q: How do I fix CVE-2018-7226?

vncterm: upgrade to newer than 0.9.10. Exact commands for each OS are on this page.

Q: Is CVE-2018-7226 being exploited?

CVE-2018-7226 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2018-7226 affect?

CVE-2018-7226 affects vncterm. Severity is critical (CVSS 9.8). 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

Q: How urgent is CVE-2018-7226?

Priority 66/100. Critical severity; Remotely exploitable, no login, no user action; On your watchlist

This week

CRITICAL 9.8REMOTEWATCHLISTUPGRADE

CVE-2018-7226 is a critical-severity flaw (CVSS 9.8) affecting vncterm. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Critical severity
Remotely exploitable, no login, no user action
On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	2.6% (top 15%)
CISA exploited list	No
Weakness	CWE-190
Published	2018-02-19
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: vncterm project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2018-02-19 17:29 UTCPublished CVE record published
2026-06-17 02:02 UTCUpdated Record last modified

vncterm project vncterm UPGRADE

Affected: <= 0.9.10

Fixed in: newer than 0.9.10

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy vncterm || rpm -q vncterm || vncterm --version

2. UPGRADE to newer than 0.9.10 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade vncterm

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade vncterm

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2018-7226?

vncterm: upgrade to newer than 0.9.10. Exact commands for each OS are on this page.

Is CVE-2018-7226 being exploited?

CVE-2018-7226 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2018-7226 affect?

CVE-2018-7226 affects vncterm. Severity is critical (CVSS 9.8). 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

How urgent is CVE-2018-7226?

Priority 66/100. Critical severity; Remotely exploitable, no login, no user action; On your watchlist

References

← Back to latest CVEs