Quick answer
Direct answer
Risk scores
| CVSS metric | What it means |
|---|---|
| Attack vector (AV:L) | Local access needed |
| Attack complexity (AC:L) | Low complexity |
| Privileges required (PR:L) | Low privileges required |
| User interaction (UI:N) | No user interaction |
| Scope (S:C) | Scope changed: impact spreads beyond the component |
| Confidentiality (C:H) | High confidentiality impact |
| Integrity (I:H) | High integrity impact |
| Availability (A:H) | High availability impact |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
About Qualcomm Package Manager
CVE-2026-25255 affects Qualcomm Package Manager, a product from Qualcomm. Before acting, confirm where Qualcomm Package Manager runs in your estate, who owns it and whether it is reachable from the internet, because exposure decides real risk more than the score alone.
What the flaw is
In plain terms: Exposed dangerous function lead to privilege escalation via gRPC server.
Based on its CVSS vector, the flaw needs local or adjacent access, needs some level of access, and needs no user interaction. Apply the vendor fix and confirm exposure on internet facing and business critical assets first.
Affected versions and timeline
| Field | Detail |
|---|---|
| Product | Qualcomm Package Manager |
| Affected versions | Package Manager 3.0.125.4; Package Manager 3.0.126.7; Package Manager 3.0.127.2; Software Center 1.17.1; Software Center 1.19.1; Software Center 1.21.0 |
| Published | Sep 22, 2026 |
| Last modified | Oct 6, 2026 |
| Added to CISA KEV | Not listed |
| Assigning CNA | product-security@qualcomm.com |
How to detect it
- Inventory every instance of Qualcomm Package Manager and record the running version against the affected range above.
- Check external attack surface scans for internet facing instances of the component.
- Review logs on affected systems for unusual requests, errors or new processes around the vulnerable function.
- Confirm with an authenticated vulnerability scan once your scanner has a check for this CVE.
How to fix it
- Apply the fixed version of Qualcomm Package Manager named in the vendor advisory.
- If patching must wait, restrict network access to the affected service and put it behind authentication or a web application firewall rule.
- Rescan after the change to prove the exposure is gone, then close the ticket.
CTEM action plan
| CTEM stage | What to do for this CVE |
|---|---|
| Scope | Add every business service that depends on Qualcomm Package Manager to the current CTEM cycle. |
| Discover | Find all instances, including shadow and cloud deployments, and record versions and exposure. |
| Prioritize | Rank using EPSS and CVSS together with asset exposure and business impact. |
| Validate | Confirm the flaw is reachable and exploitable in your environment and that compensating controls work. |
| Mobilize | Assign the fix to the asset owner with a due date matched to the priority, then verify closure. |
CWE References
Technical References
Frequently asked questions
Related CVEs
Memory Corruption when processing I2C transfer requests due to a race condition between memory allocation and data copying.
Memory Corruption when multiple threads issue concurrent IOCTL requests to the device control handler due to improper synchronization and race conditions.
Memory Corruption when processing asynchronous input parameters due to improper handling of modified values between check and use.
Memory Corruption when accessing shared buffers without validation of concurrent user-mode input modifications.
Buffer overflow due to incorrect authorization in PLC FW
Memory corruption while creating a process on the digital signal processor due to allocation failure at the kernel level.
Earn your free CTEM certification.
Learn to scope, prioritize, validate and mobilize fixes for CVEs like CVE-2026-25255 with a free CTEM certification.
Beginner / Practitioner / Program Leader
Explore certifications