# CVE-2026-48581: Surface Broker SDMA Elevation of Privilege Vulnerability

> An authorized local attacker can elevate privileges on Microsoft Surface devices due to insufficient access control granularity in the Surface Broker SDMA component.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jul 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-59xf-77x2-pv8f

## What is CVE-2026-48581?

CVE-2026-48581 is a high-severity vulnerability in Microsoft Surface Go, published on 14 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Insufficient granularity of access control in Microsoft Surface allows an authorized attacker to elevate privileges locally.

Weakness: CWE-1220 (Insufficient Granularity of Access Control)

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

It affects 27 products.


Products: Microsoft Surface Go 2 1901 Firmware, Microsoft Surface Go 2 1926 Firmware, Microsoft Surface Go 2 1927 Firmware, Microsoft Surface Go 3 1901 Firmware, Microsoft Surface Go 3 1926 Firmware, Microsoft Surface Go 3 2022 Firmware, Microsoft Surface Hub 2s 85 Firmware, Microsoft Surface Hub 2s Firmware, Microsoft Surface Hub 3 50 Firmware, Microsoft Surface Hub 3 85 Firmware, Microsoft Surface Hub Firmware, Microsoft Surface Laptop 4 1950 Firmware, Microsoft Surface Laptop 4 1951 Firmware, Microsoft Surface Laptop 4 1952 Firmware, Microsoft Surface Laptop 4 1953 Firmware, Microsoft Surface Laptop 4 1958 Firmware, Microsoft Surface Laptop 4 1959 Firmware, Microsoft Surface Laptop 4 1978 Firmware, Microsoft Surface Laptop 4 1979 Firmware, Microsoft Surface Laptop Go 1943 Firmware and 7 more.

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

No fix has been published for CVE-2026-48581 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-48581 being exploited?

There is no known exploitation of CVE-2026-48581 in the wild and no public exploit code.

## Other vulnerabilities in Microsoft Surface Go

- [CVE-2025-21194](https://insights.sbomify.com/CVE-2025-21194/): Microsoft Surface Security Feature Bypass Vulnerability (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48581 and fix it if it is affected.

What it is: CVE-2026-48581 is a high-severity vulnerability in Microsoft Surface Go, published on 14 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-48581 in the wild and no public exploit code.

Affected product: Microsoft Surface Go. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-48581/ (Markdown: https://insights.sbomify.com/CVE-2026-48581/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48581
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48581
- OSV: https://osv.dev/vulnerability/CVE-2026-48581

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-48581/
Summaries are generated and may contain mistakes; the official description above is the record.