# CVE-2026-25266: Exposed dangerous function in windows host

> Memory corruption in Qualcomm Snapdragon firmware allows attackers to execute arbitrary code or escalate privileges via IOCTL commands.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **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:** 4 May 2026
- **Updated:** 4 May 2026
- **Also known as:** GHSA-x7h5-vhw2-pmff

## What is CVE-2026-25266?

CVE-2026-25266 is a medium-severity memory corruption vulnerability in Qualcomm Cologne Firmware, published on 4 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Memory corruption while processing IOCTL command when device is in power-save state.

Weakness: CWE-787 (Out-of-bounds Write), CWE-749 (Exposed Dangerous Method or Function)

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

It affects 24 products.


Products: Qualcomm Cologne Firmware, Qualcomm Fastconnect 6900 Firmware, Qualcomm Fastconnect 7800 Firmware, Qualcomm Sc8380xp Firmware, Qualcomm Snapdragon Ar1 Gen 1 Firmware, Qualcomm Wcd9378c Firmware, Qualcomm Wcd9380 Firmware, Qualcomm Wcd9385 Firmware, Qualcomm Wcn7861 Firmware, Qualcomm Wcn7880 Firmware, Qualcomm Wsa8830 Firmware, Qualcomm Wsa8832 Firmware, Qualcomm Wsa8835 Firmware, Qualcomm Wsa8840 Firmware, Qualcomm Wsa8845 Firmware, Qualcomm Wsa8845h Firmware, Qualcomm X2000077 Firmware, Qualcomm X2000086 Firmware, Qualcomm X2000090 Firmware, Qualcomm X2000092 Firmware and 4 more.

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

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

## Is CVE-2026-25266 being exploited?

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

## Other vulnerabilities in Qualcomm Cologne Firmware

- [CVE-2026-25283](https://insights.sbomify.com/CVE-2026-25283/): Stack-based Buffer Overflow in OOBM (high 8.8)
- [CVE-2026-25282](https://insights.sbomify.com/CVE-2026-25282/): Out-of-bounds Read in OOBM (high 7.9)
- [CVE-2026-57555](https://insights.sbomify.com/CVE-2026-57555/): Use After Free in DSP Service (high 7.8)
- [CVE-2026-57559](https://insights.sbomify.com/CVE-2026-57559/): Use After Free in DSP_Services (high 7.8)
- [CVE-2025-59607](https://insights.sbomify.com/CVE-2025-59607/): Untrusted Pointer Dereference in Windows Compute (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-25266 is a medium-severity memory corruption vulnerability in Qualcomm Cologne Firmware, published on 4 May 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-25266 in the wild and no public exploit code.

Affected product: Qualcomm Cologne Firmware. 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-25266/ (Markdown: https://insights.sbomify.com/CVE-2026-25266/index.md)
```

## Sources

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

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