CVE-2026-3195

HIGHPre-NVD 7.47.4
EchelonGraph scoreMEDIUM confidence

Score 7.4 from GitHub Security Advisory (severity: HIGH) published 2026-06-19. a secondary CVSS source baseline 7.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
7.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.4Exploit: None knownExposed: 0

A fix is available — apply it.

A flaw was found in QEMU. When reading input audio in the virtio-snd device input callback, the virtio_snd_pcm_in_cb function did not check whether the iov could fit the data buffer, potentially leading to a heap out-of-bounds write. This issue exists due to an incomplete fix for CVE-2024-7730.

CVSS v3
7.4
EG Score
7.4(medium)
EG Risk
33(Track)
EG Risk 33/100SSVC: Track

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
Severity74% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

June 19, 2026

Last Modified

September 1, 2026

Advisory Details (2)

Auto-updated Jun 22, 2026
Patch available. Sources: redhat.
redhat

2443817 – (CVE-2026-3195) CVE-2026-3195 qemu-kvm: virtio-snd: heap buffer overflow in virtio_snd_pcm_in_cb (incomplete fix for CVE-2024-7730)

https://bugzilla.redhat.com/show_bug.cgi?id=2443817
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-3195

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuqemu-utils (1:10.1.0+ds-5ubuntu2.6) @ questing2026-09-14ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
qemu1:10.0.2+ds-2 ... 1:10.0.8+ds-0+deb13u1 (12 versions)1:10.0.10+ds-0+deb13u1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
qemu1:10.0.2+ds-2 ... 1:10.2.1+ds-1 (31 versions)1:10.2.2+ds-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 54× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 348 total refreshes for this CVE.

  1. 2026-09-20 20:15 UTCEPSS rescore
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-17 19:30 UTCEPSS rescore
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-15 03:11 UTCEPSS rescore
  8. 2026-09-14 02:15 UTCEG score recompute
  9. 2026-09-14 02:15 UTCVendor advisory
  10. 2026-09-14 02:15 UTCGHSA enrichment
  11. 2026-09-13 16:47 UTCEPSS rescore
  12. 2026-09-13 13:10 UTCEG score recompute
  13. 2026-09-13 13:10 UTCVendor advisory
  14. 2026-09-13 13:10 UTCGHSA enrichment
  15. 2026-09-12 15:01 UTCEPSS rescore
  16. 2026-09-11 14:53 UTCEPSS rescore
  17. 2026-09-11 09:37 UTCEPSS rescore
  18. 2026-09-10 09:34 UTCEPSS rescore
  19. 2026-09-08 22:00 UTCEPSS rescore
  20. 2026-09-07 16:01 UTCEPSS rescore
  21. 2026-09-06 13:47 UTCEPSS rescore
  22. 2026-09-04 05:06 UTCEPSS rescore
  23. 2026-09-02 14:12 UTCEPSS rescore
  24. 2026-09-01 13:53 UTCEPSS rescore
  25. 2026-09-01 13:44 UTCEG score recompute
Show 75 more
  1. 2026-09-01 13:44 UTCVendor advisory
  2. 2026-09-01 13:43 UTCGHSA enrichment
  3. 2026-09-01 12:19 UTCEG score recompute
  4. 2026-09-01 12:19 UTCVendor advisory
  5. 2026-09-01 12:19 UTCGHSA enrichment
  6. 2026-09-01 04:39 UTCEPSS rescore
  7. 2026-08-30 20:49 UTCEG score recompute
  8. 2026-08-30 20:49 UTCVendor advisory
  9. 2026-08-30 20:49 UTCGHSA enrichment
  10. 2026-08-30 19:17 UTCEPSS rescore
  11. 2026-08-30 01:22 UTCEPSS rescore
  12. 2026-08-28 21:41 UTCEPSS rescore
  13. 2026-08-27 14:25 UTCEPSS rescore
  14. 2026-08-26 14:46 UTCEPSS rescore
  15. 2026-08-25 13:49 UTCEPSS rescore
  16. 2026-08-25 01:30 UTCVendor advisory
  17. 2026-08-25 01:30 UTCGHSA enrichment
  18. 2026-08-24 14:19 UTCEG score recompute
  19. 2026-08-24 14:19 UTCVendor advisory
  20. 2026-08-24 14:19 UTCGHSA enrichment
  21. 2026-08-23 22:23 UTCVendor advisory
  22. 2026-08-23 22:23 UTCGHSA enrichment
  23. 2026-08-23 11:00 UTCEG score recompute
  24. 2026-08-23 11:00 UTCVendor advisory
  25. 2026-08-23 11:00 UTCGHSA enrichment
  26. 2026-08-23 00:19 UTCEPSS rescore
  27. 2026-08-22 23:51 UTCEG score recompute
  28. 2026-08-22 23:51 UTCVendor advisory
  29. 2026-08-22 23:51 UTCGHSA enrichment
  30. 2026-08-21 23:49 UTCEPSS rescore
  31. 2026-08-21 23:39 UTCVendor advisory
  32. 2026-08-21 23:39 UTCGHSA enrichment
  33. 2026-08-21 12:30 UTCEG score recompute
  34. 2026-08-21 12:30 UTCVendor advisory
  35. 2026-08-21 12:30 UTCGHSA enrichment
  36. 2026-08-21 06:23 UTCEG score recompute
  37. 2026-08-21 06:23 UTCVendor advisory
  38. 2026-08-21 06:23 UTCGHSA enrichment
  39. 2026-08-20 22:55 UTCEPSS rescore
  40. 2026-08-20 19:14 UTCVendor advisory
  41. 2026-08-20 19:14 UTCGHSA enrichment
  42. 2026-08-20 08:05 UTCEG score recompute
  43. 2026-08-20 08:05 UTCVendor advisory
  44. 2026-08-20 08:05 UTCGHSA enrichment
  45. 2026-08-19 17:03 UTCEPSS rescore
  46. 2026-08-19 07:18 UTCEG score recompute
  47. 2026-08-19 07:18 UTCVendor advisory
  48. 2026-08-19 07:18 UTCGHSA enrichment
  49. 2026-08-18 13:48 UTCEPSS rescore
  50. 2026-08-17 13:47 UTCEPSS rescore
  51. 2026-08-17 12:29 UTCVendor advisory
  52. 2026-08-17 12:28 UTCGHSA enrichment
  53. 2026-08-17 01:18 UTCEG score recompute
  54. 2026-08-17 01:18 UTCVendor advisory
  55. 2026-08-17 01:18 UTCGHSA enrichment
  56. 2026-08-16 14:56 UTCEPSS rescore
  57. 2026-08-16 14:09 UTCVendor advisory
  58. 2026-08-16 14:09 UTCGHSA enrichment
  59. 2026-08-16 02:59 UTCEG score recompute
  60. 2026-08-16 02:59 UTCVendor advisory
  61. 2026-08-16 02:59 UTCGHSA enrichment
  62. 2026-08-16 02:14 UTCEPSS rescore
  63. 2026-08-15 15:50 UTCVendor advisory
  64. 2026-08-15 15:50 UTCGHSA enrichment
  65. 2026-08-15 04:39 UTCEG score recompute
  66. 2026-08-15 04:39 UTCVendor advisory
  67. 2026-08-15 04:39 UTCGHSA enrichment
  68. 2026-08-15 01:30 UTCEPSS rescore
  69. 2026-08-14 17:29 UTCVendor advisory
  70. 2026-08-14 17:29 UTCGHSA enrichment
  71. 2026-08-14 05:58 UTCEG score recompute
  72. 2026-08-14 05:58 UTCVendor advisory
  73. 2026-08-14 05:58 UTCGHSA enrichment
  74. 2026-08-13 22:00 UTCEPSS rescore
  75. 2026-08-13 18:49 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-3195?
CVE-2026-3195 is a high vulnerability published on June 19, 2026. A flaw was found in QEMU. When reading input audio in the virtio-snd device input callback, the virtiosndpcmincb function did not check whether the iov could fit the data buffer, potentially leading to a heap out-of-bounds write. This issue exists due to an incomplete fix for CVE-2024-7730.
When was CVE-2026-3195 disclosed?
CVE-2026-3195 was first published in the National Vulnerability Database on June 19, 2026, with the most recent update on September 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-3195 actively exploited?
CVE-2026-3195 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.4% of all scored CVEs.
What is the CVSS score of CVE-2026-3195?
CVE-2026-3195 has a CVSS v3 base score of 7.4 (NVD).
How do I remediate CVE-2026-3195?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-3195, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-3195

Explore →

Is Your Infrastructure Affected by CVE-2026-3195?

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