# CVE-2025-34449: Genymobile/scrcpy <= 3.3.3 Global Buffer Overflow

> A compromised Android device can trigger a buffer overflow in scrcpy, potentially leading to memory corruption, code execution, or denial of service on the host.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Dec 2025
- **Updated:** 23 Mar 2026
- **Also known as:** GHSA-wvmf-999m-w27j, UBUNTU-CVE-2025-34449

## What is CVE-2025-34449?

CVE-2025-34449 is a medium-severity memory corruption vulnerability in Genymobile scrcpy, published on 18 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Genymobile/scrcpy versions up to and including 3.3.3, prior to commit 3e40b24, contain a buffer overflow vulnerability in the sc_device_msg_deserialize() function. A compromised device can send crafted messages that cause out-of-bounds reads, which may result in memory corruption or a denial-of-service condition. This vulnerability may allow further exploitation on the host system.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

It affects 1 product.


Products: Genymotion Scrcpy.

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

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

## Is CVE-2025-34449 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-34449 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-34449 and fix it if it is affected.

What it is: CVE-2025-34449 is a medium-severity memory corruption vulnerability in Genymobile scrcpy, published on 18 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-34449 exists.

Affected product: Genymobile scrcpy. 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-34449/ (Markdown: https://insights.sbomify.com/CVE-2025-34449/index.md)
```

## Sources

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

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