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.
CVE-2026-3195
HIGHPre-NVD 7.47.4—
EchelonGraph scoreHIGH 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.
- CVSS v3
- 7.4
- EG Score
- 7.4(high)
- EPSS
- 2.6%
- KEV
- Not listed
Published
June 19, 2026
Last Modified
June 30, 2026
Advisory Details (2)
Auto-updated Jun 22, 2026Patch 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=2443817Vendor 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.
- CVE-2026-3195Microsoft Security Response Center (MSRC)High
Qemu-kvm: virtio-snd: heap buffer overflow in virtio_snd_pcm_in_cb (incomplete fix for cve-2024-7730)
- GHSA-x3gf-fc58-4mvjGitHub Security AdvisoriesHigh
A flaw was found in QEMU. When reading input audio in the virtio-snd device input callback, the ...
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 June 30, 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 2.6% 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
Is Your Infrastructure Affected by CVE-2026-3195?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.