Skip to main content
CVE-2024-42049VulnerabilityPublished Updated

CVE-2024-42049: n/a

Source CVE Database V5

0

Not known to be exploited · public exploit available (Exploit-DB) · CVSS 9.1 Critical · fixed in 2.8.84 : patch affected systems as a priority.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
2.1% chance of exploitation in 30 days – higher than 81% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.8.84
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 28 Jul 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE published

    on cve.org

    , t = 0

  2. First Exploit-DB entry (opens in a new tab)

    TightVNC 2.8.83 - Control Pipe Manipulation

    , 316 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

AI-suggested

To mitigate CVE-2024-42049, organizations should take the following specific actions: 1) Immediately upgrade TightVNC Server to version 2.8.84 or later once available, as this will contain the official fix. 2) Until patches are applied, restrict network access to TightVNC services by implementing firewall rules that limit connections to trusted IP addresses and internal networks only. 3) Employ network-level authentication mechanisms such as VPNs or SSH tunnels to protect remote desktop traffic from unauthorized access. 4) Disable TightVNC Server on systems where it is not essential to reduce the attack surface. 5) Monitor network traffic and system logs for unusual or unauthorized connections to the TightVNC control port. 6) Consider deploying intrusion detection/prevention systems (IDS/IPS) with signatures tuned to detect anomalous TightVNC activity. 7) Educate IT staff about the vulnerability and ensure rapid response procedures are in place for any suspicious activity. These targeted steps go beyond generic advice by focusing on access control, network segmentation, and active monitoring specific to TightVNC environments.

Description

TightVNC (Server for Windows) before 2.8.84 allows attackers to connect to the control pipe via a network connection.

References

Community reviews

Loading reviews…