BlackBerry UEM up to 12.23.0 QF8 Management Console injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.2 | $5k-$25k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in BlackBerry UEM up to 12.23.0 QF8. This issue affects some unknown processing of the component Management Console. Performing a manipulation results in input validation. This vulnerability is reported as CVE-2026-18085. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in BlackBerry UEM up to 12.23.0 QF8. It has been classified as critical. This affects an unknown functionality of the component Management Console. The manipulation with an unknown input leads to a input validation vulnerability. CWE is classifying the issue as CWE-74. The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
An Improper Input Validation in the BlackBerry UEM Management Console of BlackBerry UEM 12.23.0 QF8 and earlier allows Arbitrary File Download and Potential Denial of Service.
The advisory is shared at support.blackberry.com. This vulnerability is uniquely identified as CVE-2026-18085 since 07/28/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 08/16/2026). MITRE ATT&CK project uses the attack technique T1055 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2026-2565). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Affected
- BlackBerry BlackBerry
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 6.2VulDB Meta Temp Score: 6.2
VulDB Base Score: 5.5
VulDB Temp Score: 5.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 6.9
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: InjectionCWE: CWE-74 / CWE-707 / CWE-20
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
07/28/2026 Advisory disclosed07/28/2026 CVE reserved
07/28/2026 VulDB entry created
08/16/2026 VulDB entry last update
Sources
Advisory: support.blackberry.comStatus: Confirmed
CVE: CVE-2026-18085 (🔒)
GCVE (CVE): GCVE-0-2026-18085
GCVE (VulDB): GCVE-100-383937
CERT Bund: WID-SEC-2026-2565 - BlackBerry UEM Management Console: Mehrere Schwachstellen
Entry
Created: 07/28/2026 19:13Updated: 08/16/2026 01:54
Changes: 07/28/2026 19:13 (52), 07/29/2026 20:31 (7), 08/16/2026 01:54 (24)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.