Google Android up to 17 Camera3 Stream Splitter DeprecatedCamera3StreamSplitter.cpp returnOutputBufferLocked out-of-bounds
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $5k-$25k | 0.48- |
Summary
A vulnerability identified as problematic has been detected in Google Android 14/15/16/16-qpr2/17. This affects the function returnOutputBufferLocked of the file DeprecatedCamera3StreamSplitter.cpp of the component Camera3 Stream Splitter. Performing a manipulation results in out-of-bounds.
This vulnerability is identified as CVE-2026-58856. The attack can be initiated remotely. There is not any exploit available.
It is recommended to apply a patch to fix this issue.
Details
A vulnerability, which was classified as problematic, was found in Google Android 14/15/16/16-qpr2/17. This affects the function returnOutputBufferLocked of the file DeprecatedCamera3StreamSplitter.cpp of the component Camera3 Stream Splitter. The manipulation with an unknown input leads to a out-of-bounds vulnerability. CWE is classifying the issue as CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. This is going to have an impact on confidentiality. The summary by CVE is:
In returnOutputBufferLocked of DeprecatedCamera3StreamSplitter.cpp, there is a possible out-of-bounds read due to a missing bounds check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.
It is possible to read the advisory at source.android.com. This vulnerability is uniquely identified as CVE-2026-58856 since 07/02/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 10/05/2026).
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
Version
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.2
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
ADP CISA Base Score: 3.3
ADP CISA 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: Out-of-boundsCWE: CWE-125 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
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 reserved10/05/2026 Advisory disclosed
10/05/2026 VulDB entry created
10/05/2026 VulDB entry last update
Sources
Vendor: google.comAdvisory: source.android.com
Status: Confirmed
CVE: CVE-2026-58856 (🔒)
GCVE (CVE): GCVE-0-2026-58856
GCVE (VulDB): GCVE-100-413751
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 10/05/2026 21:24Changes: 10/05/2026 21:24 (68)
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.