CVE Intelligence
Unknown Input validation

CVE-2026-113173 — Improper Input Validation in Google Chrome

Improper input validation in UI in Google Chrome on on Android prior to 156.0.8078.47 allowed a remote attacker to potentially execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Low)

Published Oct 20, 2026 · Updated Oct 20, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: Chrome

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • No scoring signals.

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
—
No EPSS score.
Affects
Google
Chrome
CVSS base
—
Score not published yet.

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Google Chrome).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes matching the vulnerability class (input validation), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Google Chrome ≥ 156.0.8078.47 and < 156.0.8078.47 Vulnerable CVE Program (cve.org) e CISA ADP

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
8.8 CVSS 3.1 High — — CISA-ADP via CVE Program (cve.org) e CISA ADP

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-20 · Improper Input Validation

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Not enough vector or weakness data: use the affected application’s logs as a starting point.
application logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • SSVC assessment updated
    Oct 20, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 20, 2026
  • Affected products added · google/chrome
    Oct 20, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · → Received
    Oct 20, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 20, 2026 · NIST National Vulnerability Database
  • CVE published
    Oct 20, 2026 · Chrome

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 20, 2026 – Oct 20, 2026

References

2 on the record

Elsewhere on this site

Google
every CVE for this vendor
Input validation
same class
CWE-20
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-113343 Memory corruption in Sandbox in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to... 2h
  • CVE-2026-113344 Use after free in Performance in Google Chrome prior to 156.0.8078.47 allowed a remote attacker... 2h
  • CVE-2026-113340 Buffer Errors (Improper Restriction of Operations within Memory Bounds) in Google Chrome 2h
  • CVE-2026-113342 Buffer Errors (Improper Restriction of Operations within Memory Bounds) in Google Chrome 2h
  • CVE-2026-113341 Buffer Errors (Improper Restriction of Operations within Memory Bounds) in Google Chrome 2h
  • CVE-2026-113338 Use After Free in Google Chrome 2h

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No FIRST EPSS score.
  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-113173 is "Improper Input Validation in Google Chrome", rated Unknown. It affects Chrome (Google); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.