Skip to main content
Menu
CVEs

CVE

VB-Audio VB-CABLE local privilege escalation in kernel audio driver

CVE-2026-124019

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

8.5HighCNA
Exploited
No known exploitation
Fix
Fix or patch referenced
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. VB-CABLE driver version 10.0.10011.16384 or earlier (vbaudio_cable64_win10.sys). The accessible low-integrity KS filter device object is reachable by the attacker.

Published
Last modified
Reference
Last checked
14/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub

Summary

VB-Audio VB-CABLE, a virtual audio driver, contains flaws in how its kernel driver handles certain audio property requests. A local attacker with a standard user account can use these to corrupt kernel memory or read kernel memory, which can lead to full privilege escalation or a system crash.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original description

VB-Audio VB-CABLE virtual audio device kernel streaming driver (vbaudio_cable64_win10.sys 10.0.10011.16384) contains out-of-bounds read and write vulnerabilities in its KSPROPSETID_Audio MUTE, VOLUMELEVEL, and PEAKMETER2 property handlers that allow a local standard user to supply an all-channels sentinel value which is improperly used as a loop terminator or array index instead of being bounds-checked. Attackers can exploit the accessible low-integrity KS filter device object to write attacker-controlled values sequentially into kernel memory corrupting kernel globals and object pointers, or read past an array boundary to leak kernel memory, resulting in local privilege escalation or denial of service via a kernel bug check.

Who should check

Windows teams running the VB-CABLE virtual audio driver version 10.0.10011.16384 or earlier, including vbaudio_cable64_win10.sys.

“Affecting VB-CABLE <= 10.0.10011.16384”

vulncheck.com

cve.now Index

14Pcve.now Index 14 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure5/25Specific setups only
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.5/10CVSS 8.5
  • No patch0/5No signal

What would change the score

  • Would score about 64 if added to CISA KEV
  • Would score about 59 if CISA's SSVC rates exploitation active
  • Would score about 24 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    VB-CABLE driver version 10.0.10011.16384 or earlier (vbaudio_cable64_win10.sys). The accessible low-integrity KS filter device object is reachable by the attacker.
  • Apply the patch listed under Evidence.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-124019 (VB-Audio VB-CABLE Kernel Driver Out-of-Bounds Write), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-124019 (entry last updated 2026-11-16):
Affected:
- VB-Audio VB-CABLE: through 10.0.10011.16384
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- VB-CABLE driver version 10.0.10011.16384 or earlier (vbaudio_cable64_win10.sys). (source: https://www.vulncheck.com/advisories/vb-audio-vb-cable-kernel-driver-out-of-bounds-write)
- The accessible low-integrity KS filter device object is reachable by the attacker. (source: https://www.vulncheck.com/advisories/vb-audio-vb-cable-kernel-driver-out-of-bounds-write)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, low-privilege login, no user action.
CISA KEV: CVE-2026-124019 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-124019 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://vb-audio.com/Cable/index.htm
- https://www.vulncheck.com/advisories/vb-audio-vb-cable-kernel-driver-out-of-bounds-write
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-124019
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-124019"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • VB-Audio VB-CABLE

    through 10.0.10011.16384

Evidence 4

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 2

  1. Patch
  2. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-124019

Is CVE-2026-124019 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

The VB-CABLE kernel driver has an out-of-bounds write. Its impact is local privilege escalation or denial of service through a kernel bug check. An attacker can also write values into kernel memory or read kernel memory past an array boundary.Source: vulncheck.com

Which versions are affected by CVE-2026-124019?

VB-CABLE: through 10.0.10011.16384.Source: cve.now feed data

Am I affected, and how do I check?

Versions of VB-CABLE up to and including 10.0.10011.16384 are in the affected range. The relevant driver file is vbaudio_cable64_win10.sys, and its version can be checked in Device Manager or in the file's properties. The exposure also depends on the accessible low-integrity KS filter device object, which is the reachable path for the issue.Source: vulncheck.com

How do I fix CVE-2026-124019?

The checked facts name no fixed version and no vendor patch identifiers. Check the VB-Audio VB-CABLE download page for a build newer than 10.0.10011.16384.Source: vulncheck.com