BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-0157High confidence

This could lead to remote information disclosure with no additional execution privileges needed

Google · Android

4.3MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Fix not verified
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.17% for the current model date.

Compensating controls

  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Google Android and falls inside the recorded affected range.
  2. Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-37191

No EUVD known-exploited evidence

In RtcpHeader::decodeRtcpHeader, there is a possible OOB read due to a missing bounds check. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
4.3 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Fix not verified
01

What, why and how

In RtcpHeader::decodeRtcpHeader, there is a possible OOB read due to a missing bounds check. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

What

In RtcpHeader::decodeRtcpHeader, there is a possible OOB read due to a missing bounds check. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

Why

The product reads data past the end, or before the beginning, of the intended buffer.

How

An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may obtain information outside the intended access boundary.

What

In RtcpHeader::decodeRtcpHeader, there is a possible OOB read due to a missing bounds check. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

Why

The product reads data past the end, or before the beginning, of the intended buffer.

How

An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may obtain information outside the intended access boundary.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Out-of-bounds Read → obtain information outside the intended access boundary
Attack surface
Network
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-125 ↗

CWE-125: Out-of-bounds Read. The product reads data past the end, or before the beginning, of the intended buffer.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CLowConfidentiality impact: A successful attack can cause a limited loss.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkCWE-125
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-37191Official EUVD mapping

In RtcpHeader::decodeRtcpHeader, there is a possible OOB read due to a missing bounds check. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

Official EUVD record ↗
BSI · German · WID-SEC-2026-1980Pixel Patchday Juni 2026: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Google Android Pixel ausnutzen, um sich erweiterte Berechtigungen zu verschaffen, beliebigen Code auszuführen, einen Denial-of-Service-Zustand herbeizuführen und vertrauliche Informationen offenzulegen.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0779Multiples vulnérabilités dans Google Pixel

.cve.org/CVERecord?id=CVE-2026-0148 Référence CVE CVE-2026-0149 https://www.cve.org/CVERecord?id=CVE-2026-0149 Référence CVE CVE-2026-0150 https://www.cve.org/CVERecord?id=CVE-2026-0150 Référence CVE CVE-2026-0151 https://www.cve.org/CVERecord?id=CVE-2026-0151 Référence CVE CVE-2026-0152 https://www.cve.org/CVERecord?id=CVE-2026-0152 Référence CVE CVE-2026-0153 https://www.cve.org/CVERecord?id=CVE-2026-0153 Référence CVE CVE-2026-0154 https://www.cve.org/CVERecord?id=CVE-2026-0154 Référence CVE CVE-2026-0155 https://www.cve.org/CVERecord?id=CVE-2026-0155 Référence CVE CVE-2026-0156 https://www.cve.org/CVERecord?id=CVE-2026-0156 Référence CVE CVE-2026-0157 https://www.cve.org/CVERecord?id=CVE-2026-0157 Référence CVE CVE-2026-0158 https://www.cve.org/CVERecord?id=CVE-2026-0158 Référence CVE CVE-2026-0160 https://www.cve.org/CVERecord?id=CVE-2026-0160 Référence CVE CVE-2026-0161 https://www.cve.org/CVERecord?id=CVE-2026-0161 Référence CVE CVE-2026-0162 https://www.cve.org/CVERecord?id=CVE-2026-0162 Référence CVE CVE-2026-0164 https://www.cve.org/CVERecord?id=CVE-2026-0164 Référence CVE CVE-2026-0165 https://www.cve.org/CVERecord?id=CVE-2026-0165 Référence CVE CVE-2026-24077 https://www.cve.org/CVERecord?id=CVE-2026-24077 Gestion détaillée du document le 19 juin 2026 Version initiale Alertes Avis

Official advisory ↗
CSIRT Italia · Italian · aggiornamento-di-sicurezza-per-dispositivi-google-pixel-3Aggiornamento di sicurezza per dispositivi Google Pixel

, con patch di sicurezza precedenti a giugno 2026 Azioni di mitigazione In linea con le dichiarazioni del vendor, si consiglia di aggiornare i prodotti vulnerabili seguendo le indicazioni riportate nel bollettino di sicurezza, disponibile al link presente nella sezione Riferimenti. Di seguito sono riportate le sole CVE relative alle vulnerabilità con gravità “critica” e “alta”: CVE (31) Cerca: Tabella CVE CVE POC EXPLOITATION CVE-2026-0165 : apre una nuova finestra - - CVE-2026-0164 : apre una nuova finestra - - CVE-2026-0162 : apre una nuova finestra - - CVE-2026-0161 : apre una nuova finestra - - CVE-2026-0160 : apre una nuova finestra - - CVE-2026-0157 : apre una nuova finestra - - CVE-2026-0155 : apre una nuova finestra - - CVE-2026-0154 : apre una nuova finestra - - CVE-2026-0153 : apre una nuova finestra - - CVE-2026-0152 : apre una nuova finestra - - CVE-2026-0151 : apre una nuova finestra - - CVE-2026-0150 : apre una nuova finestra - - CVE-2026-0149 : apre una nuova finestra - - CVE-2026-0148 : apre una nuova finestra - - CVE-2026-0147 : apre una nuova finestra - - CVE-2026-0146 : apre una nuova finestra - - CVE-2026-0145 : apre una nuova finestra - - CVE-2026-0142 : apre una nuova finestra - - CVE-2026-0141 : apre una nuova finestra - - CVE-2026-0140 : apre una nuova finestra - - CVE

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix not verified
Affected
Android: Android kernel
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 16 Jun 2026 · Last source change 16 Sept 2026, 16:05 UTC · CWE-125 · Out-of-bounds Read

CVE recordCVE.org · 5.2
CVSS sourceCISA ADP
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-37191
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCISA ADP
NVD statusNVD enrichment underway

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    Android kernel · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    Android: Android kernel · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-0157 · cve.blacktree.nl