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

Google Chrome — Improper Input Validation

Google · Chrome

8.6HighCVSS 3.1
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Fix not verified
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

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

Compensating controls

  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Google Chrome 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: Within 30 daysRemediation target: Within 180 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.

Distribution package intelligence

Release-specific package status

Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

4 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcechromiumVendor fix publishedDebian records a fixed source-package version for this release.151.0.7922.108-1~deb13u1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcechromiumVendor fix publishedDebian records a fixed source-package version for this release.151.0.7922.108-1~deb12u1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcechromiumVendor fix publishedDebian records a fixed source-package version for this release.151.0.7922.108-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcechromiumVendor fix publishedDebian records a fixed source-package version for this release.151.0.7922.108-1Debian Security Tracker ↗Source updated 6 Oct 2026
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-54115

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

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
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Fix not verified
01

What, why and how

Insufficient validation of untrusted input in WebAPKs in Google Chrome on Android prior to 151.0.7922.109 allowed a local attacker to potentially perform a sandbox escape via a malicious file. (Chromium security severity: High)

What

Insufficient validation of untrusted input in WebAPKs in Google Chrome on Android prior to 151.0.7922.109 allowed a local attacker to potentially perform a sandbox escape via a malicious file. (Chromium security severity: High)

Why

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How

An attacker operating through local access may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Insufficient validation of untrusted input in WebAPKs in Google Chrome on Android prior to 151.0.7922.109 allowed a local attacker to potentially perform a sandbox escape via a malicious file. (Chromium security severity: High)

Why

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How

An attacker operating through local access may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

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
local access → Improper Input Validation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
None: unauthenticated exploitation is possible
User interaction
Required interaction required
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Changed: exploitation can affect a different security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-20 ↗

CWE-20: Improper Input Validation. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

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

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

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SChangedScope: The attack can affect a component governed by a different security authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
UnauthenticatedCWE-20
A

Official authority intelligence

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

BSI · German · WID-SEC-2026-2695Google Chrome und Microsoft Edge: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Google Chrome und Microsoft Edge ausnutzen, um beliebigen Programmcode auszuführen, vertrauliche Informationen offenzulegen, Daten zu manipulieren oder einen Denial-of-Service-Zustand herbeizuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260812Security Bulletin 12 Aug 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 12 Aug 2026, published on 12 August 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

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

mentation). Documentation Bulletin de sécurité Google Chrome du 06 août 2026 https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_01193673229.html Référence CVE CVE-2026-19137 https://www.cve.org/CVERecord?id=CVE-2026-19137 Référence CVE CVE-2026-19138 https://www.cve.org/CVERecord?id=CVE-2026-19138 Référence CVE CVE-2026-19139 https://www.cve.org/CVERecord?id=CVE-2026-19139 Référence CVE CVE-2026-19140 https://www.cve.org/CVERecord?id=CVE-2026-19140 Référence CVE CVE-2026-19141 https://www.cve.org/CVERecord?id=CVE-2026-19141 Référence CVE CVE-2026-19142 https://www.cve.org/CVERecord?id=CVE-2026-19142 Référence CVE CVE-2026-19143 https://www.cve.org/CVERecord?id=CVE-2026-19143 Référence CVE CVE-2026-19144 https://www.cve.org/CVERecord?id=CVE-2026-19144 Référence CVE CVE-2026-19145 https://www.cve.org/CVERecord?id=CVE-2026-19145 Référence CVE CVE-2026-19146 https://www.cve.org/CVERecord?id=CVE-2026-19146 Référence CVE CVE-2026-19147 https://www.cve.org/CVERecord?id=CVE-2026-19147 Référence CVE CVE-2026-19148 https://www.cve.org/CVERecord?id=CVE-2026-19148 Référence CVE CVE-2026-19149 https://www.cve.org/CVERecord?id=CVE-2026-19149 Référence CVE CVE-2026-19150 https://www.cve.org/CVERecord?id=CVE-2026-19150 Référence CVE CVE-2026-19151 https://www.cve.org/CVERecord?id=

Official advisory ↗
CSIRT Italia · Italian · risolte-vulnerabilita-in-google-chrome-66Risolte vulnerabilità in Google Chrome

nuova finestra - - CVE-2026-19157 : apre una nuova finestra - - CVE-2026-19156 : apre una nuova finestra - - CVE-2026-19155 : apre una nuova finestra - - CVE-2026-19154 : apre una nuova finestra - - CVE-2026-19153 : apre una nuova finestra - - CVE-2026-19152 : apre una nuova finestra - - CVE-2026-19151 : apre una nuova finestra - - CVE-2026-19150 : apre una nuova finestra - - CVE-2026-19149 : apre una nuova finestra - - CVE-2026-19148 : apre una nuova finestra - - CVE-2026-19147 : apre una nuova finestra - - CVE-2026-19146 : apre una nuova finestra - - CVE-2026-19145 : apre una nuova finestra - - CVE-2026-19144 : apre una nuova finestra - - CVE-2026-19143 : apre una nuova finestra - - CVE-2026-19142 : apre una nuova finestra - - CVE-2026-19141 : apre una nuova finestra - - CVE-2026-19140 : apre una nuova finestra - - CVE-2026-19139 : apre una nuova finestra - - CVE-2026-19138 : apre una nuova finestra - - CVE-2026-19137 : apre una nuova finestra - - Riferimenti (1) https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_01193673229.html Change log Titolo della tabella Versione Note Data 1.0 Pubblicato il 07-08-2026 07/08/2026 Impatto sistemico Alto (66.15) Argomenti Google Chrome Data pubblicazione 07/08/26 ore 11:43 Data Ultimo Aggiornamento 07/08/26 ore 11:43 Informa

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-027467GoogleのGoogle Chromeにおける入力確認に関する脆弱性

Android版Google Chromeの151.0.7922.109未満のバージョンにおいて、WebAPKsの信頼できない入力の検証が不足していたため、ローカル攻撃者が悪意のあるファイルを利用してサンドボックスを脱出する可能性がありました。(Chromiumセキュリティの深刻度:高です)

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
Chrome: 151.0.7922.109 < 151.0.7922.109
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. Limit untrusted access and use least privilege until authoritative guidance is available.
Official vendor articles1 stored document

Linked articles are downloaded and versioned as source evidence. A CVE mention or approved update relationship does not, by itself, verify a fix for every product branch.

  • Chrome Releases: Stable Channel Update for Desktop →Original publisher ↗Searchable text snapshot · Captured 26 Sep 2026Chrome Releases Release updates from the Chrome team Stable Channel Update for Desktop Thursday, August 6, 2026 The Stable channel has been updated to 151.0.7922.108/.109 for Windows and Mac and 151.0.7922.108 for Linux, which will roll out over the coming days/weeks. A full list of changes in this build is available i
04

Evidence and provenance

Published 6 Aug 2026 · Last source change 8 Aug 2026, 03:55 UTC · CWE-20 · Improper Input Validation

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-54115
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD enriched

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

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

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-19143 · cve.blacktree.nl