CVE-2026-56915

Analyzed Analyzed - Analysis Complete

Privilege Escalation via Race Condition in Bigo

Publication date: 2026-09-15

Last updated on: 2026-09-21

Assigner: Google Devices

Description

In bigo_worker_thread of bigo.c, there is a possible escalation of privilege due to a race condition. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-09-15

Last Modified

2026-09-21

Generated

2026-10-06

AI Q&A

2026-09-16

EPSS Evaluated

2026-10-04

NVD

CVE-2026-56915

EUVD

EUVD-2026-78963

Affected Vendors & Products

Vendor	Product	Version / Range
google	android	*

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-362	The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

Attack-Flow Graph

Executive Summary

This vulnerability is a race condition in the bigo_worker_thread function of bigo.c. It allows an attacker to escalate privileges locally, requiring system execution privileges to exploit. No user interaction is needed.

Impact Analysis

An attacker could exploit this to gain higher privileges on your system, potentially allowing them to execute arbitrary code with elevated permissions. This could lead to unauthorized access or control of your device.

Compliance Impact

This vulnerability could lead to local privilege escalation with system execution privileges, potentially allowing unauthorized access to sensitive data. This may impact compliance with standards like GDPR and HIPAA by increasing the risk of data breaches or unauthorized data access.

Mitigation Strategies

Apply patches or updates from the vendor if available. Monitor for unusual privilege escalation events. Restrict access to systems where this vulnerability could be exploited.

Hi! I’m here to help you understand CVE-2026-56915. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70