Skip to main content

Windows Audio Service EUVDEUVD-2026-100401

| CVE-2026-97799 HIGH
Improper Verification of Cryptographic Signature (CWE-347)
2026-10-13 secure@microsoft.com GHSA-xwxp-p8cr-2wjq
7.8
CVSS 3.1 · Vendor: microsoft
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as low-privileged local user
  2. Exploit
    Craft payload with forged/invalid signature
  3. Execution
    Bypass signature verification in Windows Audio Service
  4. Impact
    Execute code with SYSTEM privileges

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Signature verification
Exploitation Conditions

Exploitation requires the attacker to already hold a local, authenticated low-privilege account on an affected Windows 11 host (24H2 below 10.0.26100.9711, 25H2 below 10.0.26200.9711, 26H1 below 10.0.28000.3231, or 26H2 below 10.0.26300.9711) and to interact with the Windows Audio Service, abusing its improper cryptographic signature verification to have attacker-controlled content treated as trusted. Limiting factors that reduce real-world risk: no remote vector (local access only), a valid authenticated foothold is mandatory (PR:L), and patched builds are not exploitable; the absence of required user interaction (UI:N) and low complexity (AC:L) mean that once a foothold exists, escalation is reliable.

Impact

This is a moderately-high-priority local elevation-of-privilege flaw (CVSS 7.8) whose risk is driven by impact rather than reach. The CVSS vector confirms local attack (AV:L) with low complexity (AC:L), requiring low privileges (PR:L) and no user interaction (UI:N), yielding full confidentiality, integrity and availability impact (C:H/I:H/A:H) within an unchanged scope (S:U) - consistent with an authenticated local user escalating to SYSTEM. No EPSS score, SSVC decision, or KEV listing was provided in the input, and no POC is indicated, so exploitation likelihood cannot be quantified from the available signals; per precedent for local EoP bugs that require prior code execution on the host, this is a post-compromise amplifier rather than an initial-access or wormable threat. There is no conflict between the CVSS vector and the description - both agree on local, authenticated exploitation. The realistic verdict: a legitimate patch priority for Windows 11 fleets because of the ubiquitous footprint and SYSTEM-level impact, but not an emergency relative to remotely exploitable unauthenticated flaws, since an attacker must already have a local authenticated foothold.

Exploit ScenarioDerived

An attacker who has already gained low-privileged authenticated access to a Windows 11 machine (e.g., via phishing, a standard user account, or another foothold) crafts input that the Windows Audio Service accepts due to improper cryptographic signature verification (CWE-347), causing the service to trust attacker-controlled content and escalate the attacker to SYSTEM. No user interaction is required and attack complexity is low. No public exploit is identified at time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 13, 2026

Local privilege escalation in the Windows Audio Service lets an authenticated low-privilege user on affected Windows 11 builds (24H2, 25H2, 26H1, 26H2) have attacker-controlled content accepted as trusted, yielding high confidentiality, integrity, and availability impact at CVSS 7.8. Exploitation is local-only and requires an existing foothold (PR:L) with no user interaction (UI:N) and low complexity (AC:L), so escalation is reliable once the attacker is on the host, though limiting factors are the mandatory authenticated local access and the fact that patched builds are not exploitable. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis.

RemediationAI

Vendor-released patch: apply the Windows security update that brings affected hosts to build 10.0.26100.9711 (24H2), 10.0.26200.9711 (25H2), 10.0.28000.3231 (26H1), or 10.0.26300.9711 (26H2), as documented in the MSRC update guide at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-97799. Because exploitation requires an existing local, authenticated low-privilege account and interaction with the Windows Audio Service, compensating controls before patching include restricting interactive and RDP logon to trusted users, enabling application allowlisting to block untrusted audio components, and monitoring the Windows Audio Service for unexpected loading of unsigned or user-writable modules; these measures reduce exposure but do not fix the root signature-verification weakness and can break legitimate audio effects or third-party audio processing objects.

Affected VersionsENISA

Windows 11 Version 24H2 10.0.26100.0 <10.0.26100.9711
Windows 11 Version 25H2 10.0.26200.0 <10.0.26200.9711
Windows 11 version 26H1 10.0.28000.0 <10.0.28000.3231
Windows 11 Version 26H2 10.0.26300.0 <10.0.26300.9711

Affected Packages

euvd windows_11_version_24h2 fix: 10.0.26100.9711
euvd windows_11_version_25h2 fix: 10.0.26200.9711
euvd windows_11_version_26h1 fix: 10.0.28000.3231
euvd windows_11_version_26h2 fix: 10.0.26300.9711

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 4 packages in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The Windows Audio Service (Audiosrv) runs in user mode and brokers audio processing, including the loading and verification of audio components such as processing objects. CVE-2026-97799 is a CWE-347 flaw: the service performs improper verification of a cryptographic signature, so content controlled by a low-privilege local user can be treated as trusted. Because the service can act in a privileged security context, that trust-boundary failure enables elevation of privilege up to SYSTEM, consistent with the assessed CVSS 3.1 vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Third-party tagging mentions 'JWT Attack' and 'Information Disclosure', which suggests the vulnerable signature path may process token-like signed content and could leak data, but the authoritative assessment for this CVE is local elevation of privilege via improper signature validation on Windows 11 24H2, 25H2, 26H1, and 26H2.

Know when Windows gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (microsoft) PRIMARY 7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.8 HIGH

Local authenticated EoP: AV:L and PR:L because a low-privileged foothold is required, AC:L and UI:N for reliable triggering, S:U with full C/I/A impact from SYSTEM escalation.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Patch available
Oct 13, 2026 - 20:20 EUVD
CVE Published
Oct 13, 2026 - 19:22 nvd
HIGH 7.8

DescriptionCVE.org

Improper verification of cryptographic signature in Windows Audio Service allows an authorized attacker to elevate privileges locally.

Executive ViewAI

Why It Matters

A high-severity local privilege escalation flaw in the Windows Audio Service affects Windows 11 systems on the 24H2, 25H2, 26H1, and 26H2 release channels, allowing an attacker who already holds a low-privilege account on a device to elevate to full system control. Because the flaw cannot be reached remotely and requires an existing foothold, the primary organizational risk is post-compromise escalation on endpoints, which can turn a single phished or shared workstation into a system-level beachhead for lateral movement and data theft. Leadership should treat this as a containment and patching priority for the Windows 11 fleet, particularly for privileged-user, remote-work, and shared-device populations.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.3%
Top 79% exploitable
Prevalence
Ubiquitous
core Windows 11 OS service present in vast fraction of environments
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation More Likely
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Defer
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

39
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +39
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0
CVE-2025-52691 CRITICAL POC
10.0 Dec 29

Unauthenticated remote code execution in SmarterTools SmarterMail lets an attacker upload arbitrary files to any locatio

CVE-2019-0803 HIGH POC
7.8 Apr 09

Windows Win32k fails to properly handle objects in memory, allowing local privilege escalation exploited in the wild in

CVE-2020-1472 MEDIUM POC
5.5 Aug 17

A privilege escalation vulnerability (CVSS 5.5). Risk factors: actively exploited (KEV-listed), EPSS 94% exploitation pr

CVE-2025-33053 HIGH POC
8.8 Jun 10

Windows Internet Shortcut Files (.url) contain an external control vulnerability (CVE-2025-33053, CVSS 8.8) that enables

CVE-2025-33073 HIGH POC
8.8 Jun 10

Windows SMB contains an improper access control vulnerability (CVE-2025-33073, CVSS 8.8) enabling authenticated attacker

CVE-2025-13315 CRITICAL POC
9.3 Nov 19

Twonky Server 8.5.2 on Linux and Windows allows unauthenticated access to the admin log file through a web service API b

CVE-2013-10047 CRITICAL POC
9.3 Aug 01

An unrestricted file upload vulnerability exists in MiniWeb HTTP Server <= Build 300 that allows unauthenticated remote

CVE-2012-10030 CRITICAL POC
9.3 Aug 05

FreeFloat FTP Server contains multiple critical design flaws that allow unauthenticated remote attackers to upload arbit

CVE-2025-34101 CRITICAL POC
9.3 Jul 10

Serviio Media Server versions 1.4 through 1.8 on Windows contain an unauthenticated command injection in the /rest/actio

CVE-2025-13316 HIGH POC
8.2 Nov 19

Twonky Server 8.5.2 uses hard-coded cryptographic keys for encrypting the administrator password. Combined with the cred

CVE-2025-34095 CRITICAL POC
9.3 Jul 10

Mako Server versions 2.5 and 2.6 contain an unauthenticated OS command injection via the tutorial interface at examples/

CVE-2025-11953 CRITICAL POC
9.8 Nov 03

React Native Metro Development Server binds to external interfaces by default and contains an OS command injection endpo

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy