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.4
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.4Exploit: NoneExposed: 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
6.8%
KEV
Not listed

Published

June 19, 2026

Last Modified

July 15, 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

Vendor Advisories for CVE-2026-3195(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

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

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.

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 10× in last 7d / 121× 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 139 total refreshes for this CVE.

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

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs