CVE-2025-34449

Genymotion Scrcpy insecure deserialization

9.1 CRITICALPublic exploitEPSS 0.42%

Published18 Dec 2025

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.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityNone

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

Affected products

Genymotion Scrcpy< 3.3.4

Remediation

Fixed in

Genymotion Scrcpy≥ 3.3.4

Patch & vendor advisories

References

https://github.com/Genymobile/scrcpy/commit/3e40b24Patch
https://github.com/Genymobile/scrcpy/issues/6415ExploitIssue TrackingPatch
https://github.com/marlinkcyber/advisories/blob/main/advisories/MCSAID-2025-003-scrcpy-global-buffer-overflow.mdExploitThird Party Advisory
https://www.vulncheck.com/advisories/genymobile-scrcpy-global-buffer-overflowThird Party Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2025-34449 being actively exploited?

CVE-2025-34449 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.42%.

How severe is CVE-2025-34449?

CVE-2025-34449 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 0.42% probability of exploitation.

Which products are affected by CVE-2025-34449?

Affected products include Genymotion Scrcpy.

How do I fix CVE-2025-34449?

Upgrade affected software to a fixed version, for example Genymotion Scrcpy 3.3.4 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2025-34449 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.