Google Android cpm_mbox_srv cpm_mbox_srv/main.c get_sswrp_state information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 1.9 | $0-$5k | 0.00+ |
Summary
A vulnerability identified as problematic has been detected in Google Android. This issue affects the function get_sswrp_state of the file cpm_mbox_srv/main.c of the component cpm_mbox_srv. The manipulation leads to information disclosure.
This vulnerability is documented as CVE-2026-58806. The attack needs to be performed locally. There is not any exploit available.
It is recommended to apply a patch to fix this issue.
Details
A vulnerability was found in Google Android (affected version not known) and classified as problematic. This issue affects the function get_sswrp_state of the file cpm_mbox_srv/main.c of the component cpm_mbox_srv. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. The summary by CVE is:
In get_sswrp_state of cpm_mbox_srv/main.c, there is a possible Logic error due to a logic error in the code. This could lead to local information disclosure with execution privileges needed. User interaction is for exploitation.
It is possible to read the advisory at source.android.com. The identification of this vulnerability is CVE-2026-58806 since 07/02/2026. The exploitation is known to be easy. Attacking locally is a requirement. The exploitation needs additional levels of successful authentication. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.
Applying a patch is able to eliminate this problem.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 2.0VulDB Meta Temp Score: 1.9
VulDB Base Score: 2.0
VulDB Temp Score: 1.9
VulDB Vector: 🔒
VulDB Reliability: 🔍
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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔒
Status: Not defined
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: PatchStatus: 🔍
0-Day Time: 🔒
Timeline
07/02/2026 CVE reserved11/10/2026 Advisory disclosed
11/10/2026 VulDB entry created
11/10/2026 VulDB entry last update
Sources
Vendor: google.comAdvisory: source.android.com
Status: Confirmed
CNA: Google_Devices
CVE: CVE-2026-58806 (🔒)
GCVE (CVE): GCVE-0-2026-58806
GCVE (VulDB): GCVE-100-434471
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 11/10/2026 21:09Changes: 11/10/2026 21:09 (58)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.