Skip to main content
VulnerabilityPublished

CVE-2025-27063: Qualcomm Snapdragon · Use After Free

Affects Qualcomm SnapdragonSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.09% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

  1. Monitor Qualcomm and device vendors for official patches addressing CVE-2025-27063 and apply them promptly across all affected devices and platforms.
  2. Implement strict access controls to limit local access to devices running vulnerable Snapdragon components, reducing the attack surface.
  3. Employ runtime protections such as memory protection mechanisms (e.g., DEP, ASLR) and sandboxing where possible to mitigate exploitation of memory corruption vulnerabilities.
  4. Conduct thorough inventory and asset management to identify all devices using affected Qualcomm platforms within the organization.
  5. For critical infrastructure, consider network segmentation and isolation of vulnerable devices to contain potential exploitation impact.
  6. Enhance monitoring and anomaly detection for unusual video playback operations or crashes that may indicate exploitation attempts.
  7. Collaborate with suppliers and OEMs to ensure timely firmware and software updates are integrated into device management workflows.
  8. Educate security teams about the vulnerability specifics to improve incident detection and response readiness.
  9. Where patching is delayed, consider temporary mitigations such as disabling video playback features or restricting related services if feasible.
  10. Participate in information sharing with industry groups and CERTs to stay informed on emerging exploits and mitigation strategies.

Description

Memory corruption during video playback when video session open fails with time out error.

References

Community reviews

Loading reviews…