# CVE-2025-59613: Stack-based Buffer Overflow in Windows Compute

> A stack-based buffer overflow in Qualcomm Snapdragon firmware allows attackers to execute arbitrary code or escalate privileges via malformed data.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jun 2026
- **Updated:** 2 Jun 2026
- **Also known as:** GHSA-6q6f-f265-rx66

## What is CVE-2025-59613?

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

### Official description

Memory Corruption when output buffer size is smaller than input buffer size during data copying operation.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2025-59613?

It affects 44 products.


Products: Qualcomm Cologne Firmware, Qualcomm Fastconnect 6700 Firmware, Qualcomm Fastconnect 6900 Firmware, Qualcomm Fastconnect 7800 Firmware, Qualcomm Iqx5121 Firmware, Qualcomm Iqx7181 Firmware, Qualcomm Qca0000 Firmware, Qualcomm Qcm5430 Firmware, Qualcomm Qcm6490 Firmware, Qualcomm Sc8380xp Firmware, Qualcomm Sd865 5g Firmware, Qualcomm Snapdragon 460 Mobile Platform Firmware, Qualcomm Snapdragon 662 Mobile Platform Firmware, Qualcomm Snapdragon 7c\+ Gen 3 Compute Firmware, Qualcomm Snapdragon 8cx Gen 3 Compute Platform Firmware, Qualcomm Snapdragon Ar1 Gen 1 Platform Firmware, Qualcomm Snapdragon Xr2\+ Gen 1 Platform Firmware, Qualcomm Snapdragon Xr2 5g Platform Firmware, Qualcomm Sxr2230p Firmware, Qualcomm Sxr2250p Firmware and 24 more.

## How do I fix CVE-2025-59613?

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

## Is CVE-2025-59613 being exploited?

There is no known exploitation of CVE-2025-59613 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-2025-59613 and fix it if it is affected.

What it is: CVE-2025-59613 is a medium-severity memory corruption vulnerability in Qualcomm Cologne Firmware, published on 1 Jun 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-2025-59613 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-2025-59613/ (Markdown: https://insights.sbomify.com/CVE-2025-59613/index.md)
```

## Sources

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

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