CVE-2009-3616

CRITICALNVD 9.99.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 9.9 from GitHub Security Advisory (severity: HIGH) published 2022-05-02. NVD baseline CVSS 9.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
9.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 3.9%CVSS: 9.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Multiple use-after-free vulnerabilities in vnc.c in the VNC server in QEMU 0.10.6 and earlier might allow guest OS users to execute arbitrary code on the host OS by establishing a connection from a VNC client and then (1) disconnecting during data transfer, (2) sending a message using incorrect integer data types, or (3) using the Fuzzy Screen Mode protocol, related to double free vulnerabilities.

CVSS v3
9.9
EG Score
9.9CRITICALmedium confidence
EG Risk
46
EG Risk 46/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity99% × 45%
The EG Score, 9.9 of 10.
Exploitation3.9% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
3.9%
EPSS %ILE
89th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 23, 2009

Last Modified

April 23, 2026

Advisory Details (8)

Auto-updated Oct 12, 2026
Patch available. Sources: redhat.
Red HatMentions a patch (unverified)

508567 – Virtual Machine aborts abrupt when executing rdesktop localhost:5900 command

https://bugzilla.redhat.com/show_bug.cgi?id=508567
Red HatMentions a patch (unverified)

505641 – CVE-2009-3616 Remote VNC client can cause any QEMU VNC server to crash with a double-free

Affected: Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please

https://bugzilla.redhat.com/show_bug.cgi?id=505641
Red HatMentions a patch (unverified)

501131 – qemu segfault when VNC client disconnects

https://bugzilla.redhat.com/show_bug.cgi?id=501131
Web page

CVE-2009-3616 - PSIRT.COM

http://www.securityfocus.com/bid/36716
Web page

oss-security - Re: QEMU VNC use-after-free

http://www.openwall.com/lists/oss-security/2009/10/16/8
Web page

oss-security - QEMU VNC use-after-free

http://www.openwall.com/lists/oss-security/2009/10/16/5
Web page
http://rhn.redhat.com/errata/RHEA-2009-1272.html
Web page

'Re: [Qemu-devel] [STABLE] [BUG] VNC mode can crash QEMU' - MARC

http://marc.info/?l=qemu-devel&m=124324043812915

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
qemu—
  • every version up to 0.11.0-1: fixed in 0.11.0-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
qemu—
  • every version up to 0.11.0-1: fixed in 0.11.0-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
qemu—
  • every version up to 0.11.0-1: fixed in 0.11.0-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
qemu—
  • every version up to 0.11.0-1: fixed in 0.11.0-1
—

Data Freshness Timeline

(refreshed 8× in last 7d / 19× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 83 of 126 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 17 repeat rows among the latest 100 are merged into the row they repeat. The 43 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-12 01:52 UTCEG score recompute
  2. 2026-10-11 13:38 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  3. 2026-10-10 19:54 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  4. 2026-10-09 20:00 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  5. 2026-10-08 16:33 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  6. 2026-10-07 23:37 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  7. 2026-10-06 15:09 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  8. 2026-10-05 17:37 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  9. 2026-10-04 00:19 UTCOSV refresh
  10. 2026-09-30 14:58 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  11. 2026-09-29 08:00 UTCEG score recompute
  12. 2026-09-27 13:39 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  13. 2026-09-26 15:52 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  14. 2026-09-24 13:57 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  15. 2026-09-17 19:20 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  16. 2026-09-15 03:04 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  17. 2026-09-14 14:14 UTCOSV refresh
  18. 2026-09-13 16:40 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  19. 2026-09-12 14:54 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  20. 2026-09-10 09:24 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  21. 2026-09-06 13:41 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  22. 2026-09-05 15:22 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  23. 2026-09-04 13:55 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  24. 2026-08-28 21:34 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  25. 2026-08-27 14:19 UTCEPSS rescoreEPSS 3.9% · 89th percentile
Show 58 more
  1. 2026-08-26 15:06 UTCOSV refresh
  2. 2026-08-25 13:43 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  3. 2026-08-19 16:58 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  4. 2026-08-15 01:24 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  5. 2026-08-10 04:09 UTCOSV refresh
  6. 2026-08-09 13:41 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  7. 2026-08-08 16:31 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  8. 2026-08-06 13:41 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  9. 2026-08-03 10:28 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  10. 2026-07-30 16:22 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  11. 2026-07-30 01:26 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  12. 2026-07-25 14:12 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  13. 2026-07-25 04:41 UTCOSV refresh
  14. 2026-07-24 14:12 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  15. 2026-07-23 14:14 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  16. 2026-07-23 01:00 UTCEG score recompute
  17. 2026-07-23 00:37 UTCEG score recompute
  18. 2026-07-23 00:04 UTCEG score recompute
  19. 2026-07-22 21:43 UTCEG score recompute
  20. 2026-07-22 14:03 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  21. 2026-07-21 15:20 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  22. 2026-07-20 17:03 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  23. 2026-07-18 09:59 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  24. 2026-07-16 16:58 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  25. 2026-07-15 16:54 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  26. 2026-07-15 01:55 UTCEPSS rescoreEPSS 3.9% · 88th percentile
  27. 2026-07-13 22:25 UTCEPSS rescoreEPSS 3.9% · 88th percentile
  28. 2026-07-11 08:22 UTCEPSS rescoreEPSS 3.9% · 88th percentile
  29. 2026-07-09 19:04 UTCEPSS rescoreEPSS 3.9% · 88th percentile
  30. 2026-07-08 15:10 UTCEPSS rescoreEPSS 3.9% · 88th percentile
  31. 2026-07-07 23:27 UTCOSV refresh
  32. 2026-07-06 16:23 UTCEPSS rescoreEPSS 3.9% · 88th percentile
  33. 2026-07-06 02:19 UTCEPSS rescoreEPSS 3.9% · 88th percentile
  34. 2026-07-05 02:26 UTCEPSS rescoreEPSS 3.9% · 88th percentile
  35. 2026-07-04 06:27 UTCEPSS rescoreEPSS 3.9% · 88th percentile
  36. 2026-07-01 15:02 UTCEPSS rescoreEPSS 3.9% · 88th percentile
  37. 2026-06-30 23:19 UTCEPSS rescoreEPSS 3.9% · 88th percentile
  38. 2026-06-28 14:03 UTCEPSS rescoreEPSS 3.9% · 88th percentile
  39. 2026-06-28 04:52 UTCEPSS rescoreEPSS 3.9% · 88th percentile
  40. 2026-06-27 03:05 UTCEPSS rescoreEPSS 3.9% · 88th percentile
  41. 2026-06-25 13:46 UTCEPSS rescoreEPSS 3.9% · 88th percentile
  42. 2026-06-24 14:02 UTCEPSS rescoreEPSS 3.9% · 88th percentile
  43. 2026-06-23 21:29 UTCEPSS rescoreEPSS 3.9% · 88th percentile
  44. 2026-06-21 14:53 UTCEPSS rescoreEPSS 3.9% · 88th percentile
  45. 2026-06-21 01:56 UTCEPSS rescoreEPSS 3.9% · 88th percentile
  46. 2026-06-19 19:22 UTCEPSS rescoreEPSS 3.9% · 88th percentile
  47. 2026-06-19 11:25 UTCOSV refresh
  48. 2026-06-18 17:49 UTCEPSS rescoreEPSS 3.9% · 88th percentile
  49. 2026-06-17 17:49 UTCEPSS rescoreEPSS 3.9% · 88th percentile
  50. 2026-06-16 17:49 UTCEPSS rescoreEPSS 3.9% · 88th percentile
  51. 2026-06-15 17:44 UTCEPSS rescoreEPSS 3.9% · 88th percentile
  52. 2026-06-14 23:14 UTCEPSS rescoreEPSS 0.8% · 73rd percentile
  53. 2026-06-13 22:57 UTCEPSS rescoreEPSS 0.8% · 73rd percentile
  54. 2026-06-12 23:08 UTCEPSS rescoreEPSS 0.8% · 73rd percentile
  55. 2026-06-10 22:14 UTCEPSS rescoreEPSS 0.8% · 73rd percentile
  56. 2026-06-10 13:17 UTCEPSS rescoreEPSS 0.8% · 73rd percentile
  57. 2026-06-08 14:13 UTCEPSS rescoreEPSS 0.8% · 73rd percentile
  58. 2026-06-07 15:22 UTCEPSS rescoreEPSS 0.8% · 73rd percentile

Related CVEs(same product)

Frequently asked(5)

What is CVE-2009-3616?
CVE-2009-3616 is a critical-severity vulnerability; its CVE record was published on October 23, 2009. Multiple use-after-free vulnerabilities in vnc.c in the VNC server in QEMU 0.10.6 and earlier might allow guest OS users to execute arbitrary code on the host OS by establishing a connection from a VNC client and then (1) disconnecting during data transfer, (2) sending a message using incorrect…
When was CVE-2009-3616 made public?
CVE-2009-3616 was made public on October 16, 2009: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on October 23, 2009. EchelonGraph's copy of the record carries a last-modified date of April 23, 2026; the record at its source may have been updated since.
Is CVE-2009-3616 actively exploited?
CVE-2009-3616 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.9% probability of exploitation in the next 30 days (89th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2009-3616?
CVE-2009-3616 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2009-3616?
A fix for CVE-2009-3616 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2009-3616

Explore →

Is Your Infrastructure Affected by CVE-2009-3616?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs