BlackBerry maintains a focused but security-critical portfolio centered on the QNX real-time operating system, enterprise mobility management, and endpoint security platforms that span embedded systems, servers, and managed device fleets. Vulnerabilities affecting the vendor skew toward serious outcomes, with an elevated share reaching critical severity and a moderate tendency toward public exploit availability, reflecting the high-value nature of endpoint management and embedded operating-system targets. The exposure recurs across products including QNX, the Unified Endpoint Manager, and enterprise server infrastructure through weakness classes spanning cross-site scripting, input validation failures, memory-safety issues, and sensitive-information disclosure—patterns consistent with both web-facing administrative interfaces and low-level system software. QNX in particular represents a durable legacy presence in automotive, industrial control, and embedded environments where patching cycles are lengthy and exposure windows extended. Current exploitation activity, severity distribution, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by BlackBerry over time
Of all the CVEs published by BlackBerry as a CNA, 82.3% affect products that BlackBerry develops as a vendor.
Of all the CVEs published that affect products developed by BlackBerry, 58.0% are self-published by BlackBerry as a CNA.
Signals from CVEs in this vendor scope (88 CVEs).
88 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2020-1938CRITICAL When using the Apache JServ Protocol (AJP), care must be taken when trusting incoming connections to Apache Tomcat. Tomcat treats AJP connections as having higher trust than, for e | Feb 24, 2020 | 9.8 | 99 | YES | YES |
CVE-2020-11652MEDIUM An issue was discovered in SaltStack Salt before 2019.2.4 and 3000 before 3000.2. The salt-master process ClearFuncs class allows access to some methods that improperly sanitize pa | Apr 30, 2020 | 6.5 | 96 | YES | YES |
CVE-2014-2533HIGH /sbin/ifwatchd in BlackBerry QNX Neutrino RTOS 6.4.x and 6.5.x allows local users to gain privileges by providing an arbitrary program name as a command-line argument. | Mar 18, 2014 | 7.2 | 42 | NO | YES |
CVE-2016-1914HIGH Multiple SQL injection vulnerabilities in the com.rim.mdm.ui.server.ImageServlet servlet in BlackBerry Enterprise Server 12 (BES12) Self-Service before 12.4 allow remote attackers | Apr 13, 2017 | 8.8 | 39 | NO | YES |
CVE-2008-3024HIGH Stack-based buffer overflow in phgrafx in QNX Momentics (aka RTOS) 6.3.2 and earlier allows local users to gain privileges via a long .pal filename in palette/. | Jul 7, 2008 | 9.3 | 38 | NO | YES |
CVE-2021-22156CRITICAL An integer overflow vulnerability in the calloc() function of the C runtime library of affected versions of BlackBerry® QNX Software Development Platform (SDP) version(s) 6.5.0SP1 | Aug 17, 2021 | 9.8 | 32 | NO | NO |
CVE-2025-2474CRITICAL Out-of-bounds write in the PCX image codec in QNX SDP versions 8.0, 7.1 and 7.0 could allow an unauthenticated attacker to cause a denial-of-service condition or execute code in th | Jun 10, 2025 | 9.8 | 30 | NO | NO |
CVE-2021-32024CRITICAL A remote code execution vulnerability in the BMP image codec of BlackBerry QNX SDP version(s) 6.4 to 7.1 could allow an attacker to potentially execute code in the context of the a | Dec 13, 2021 | 9.8 | 30 | NO | NO |
CVE-2017-9367CRITICAL A directory traversal vulnerability in the BlackBerry Workspaces Server could potentially allow an attacker to execute or upload arbitrary files, or reveal the content of arbitrary | Oct 16, 2017 | 9.8 | 30 | NO | NO |
CVE-2025-3938CRITICAL Missing Cryptographic Step vulnerability in Tridium Niagara Framework on Windows, Linux, QNX, Tridium Niagara Enterprise Security on Windows, Linux, QNX allows Cryptanalysis. This | May 22, 2025 | 9.8 | 29 | NO | NO |
Signals from CVEs in this vendor scope (88 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by BlackBerry.
Media articles that mention a CVE ID that affects a product developed by BlackBerry — matched by CVE ID, not by vendor name.