How severe is CVE-2006-2369?

No CVSS score has been assigned to CVE-2006-2369 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2006-2369?

CVE-2006-2369 affects the following packages: vnc4 (Debian:10). Ecosystems affected: Debian:10.

How do I fix CVE-2006-2369?

Update vnc4 to 4.1.1+X4.3.0-10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2006-2369 is resolved across your whole dependency graph.

How do I detect CVE-2006-2369 in my Debian:10 dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vnc4, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2006-2369 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2006-2369 actively exploited in the wild?

Yes. There are 9 known exploit references for CVE-2006-2369, including 4 documented proof-of-concept exploits on Exploit-DB and 5 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2006-2369?

CVE-2006-2369 has an EPSS (Exploit Prediction Scoring System) score of 92.4%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2006-2369?

CVE-2006-2369 is classified as Improper Authentication (CWE-287). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2006-2369 published, and has it been updated?

CVE-2006-2369 was published on May 15, 2006 and was last updated on June 4, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Withdrawn — this advisory has been retracted

📦 Debian:10

Not in CISA KEV

CVE-2006-2369 — vnc4

CVE-2006-2369 is a Improper Authentication vulnerability in vnc4. 9 public exploit references exist, so weaponization risk is real. A fix is available for vnc4 — see the affected versions and patch details below.

Published

May 15, 2006

Updated

Jun 4, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

9 known

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

92.4%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

📦vnc4

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Debian:10 packages — download data is not available via public APIs for these ecosystems.

Description

RealVNC 4.1.1, and other products that use RealVNC such as AdderLink IP and Cisco CallManager, allows remote attackers to bypass authentication via a request in which the client specifies an insecure security type such as "Type 1 - None", which is accepted even if it is not offered by the server, as originally demonstrated using a long password.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦Debian:10	`vnc4`	all versions	4.1.1+X4.3.0-10

Affected Products

1 product · 1 configurations

Application

realvncvnc

1 version

4.1.1

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-36932remotewindows✓ Verified

RealVNC 4.1.0/4.1.1 - Authentication Bypass

by fdiskyou · May 13, 2012

Exploit-DB Source

EDB-1794remotemultiple✓ Verified

RealVNC 4.1.0 < 4.1.1 - VNC Null Authentication Bypass (Metasploit)

by H D Moore · May 15, 2006

Exploit-DB Source

EDB-1791remotemultiple✓ Verified

RealVNC 4.1.0 < 4.1.1 - VNC Null Authentication Bypass

by redsand · May 16, 2006

Exploit-DB Source

EDB-17719remotewindows✓ Verified

RealVNC - Authentication Bypass (Metasploit)

by Metasploit · Aug 26, 2011

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vnc4, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update vnc4 to 4.1.1+X4.3.0-10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2006-2369 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2006-2369 in your dependencies?

Find it across Debian:10, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2006-2369 — vnc4

EPSS Exploitation Probability

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2006-2369 in your dependencies?