Google Android Quantization Table Lookup GC2AV1Enc.cpp getCodecQp memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.6 | $5k-$25k | 0.00+ |
Summary
A vulnerability categorized as problematic has been discovered in Google Android. The affected element is the function getCodecQp of the file GC2AV1Enc.cpp of the component Quantization Table Lookup. The manipulation results in memory corruption.
This vulnerability is cataloged as CVE-2026-59619. The attack may be launched remotely. There is no exploit available.
It is advisable to implement a patch to correct this issue.
Details
A vulnerability classified as problematic has been found in Google Android (affected version unknown). Affected is the function getCodecQp of the file GC2AV1Enc.cpp of the component Quantization Table Lookup. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This is going to have an impact on confidentiality. CVE summarizes:
In getCodecQp of GC2AV1Enc.cpp, there is a possible way to trigger an out of bounds read during quantization table lookup due to a missing bounds check. This could lead to local information disclosure with System execution privileges needed. User interaction is not needed for exploitation.
The advisory is shared for download at source.android.com. This vulnerability is traded as CVE-2026-59619 since 07/06/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. Additional levels of successful authentication are needed for exploitation. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 11/10/2026).
Applying a patch is able to eliminate this problem.
Once again VulDB remains the best 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.7VulDB Meta Temp Score: 2.6
VulDB Base Score: 2.7
VulDB Temp Score: 2.6
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: Memory corruptionCWE: 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/06/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-59619 (🔒)
GCVE (CVE): GCVE-0-2026-59619
GCVE (VulDB): GCVE-100-434484
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 11/10/2026 21:11Changes: 11/10/2026 21:11 (58)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.