cve.bz

CVE-2026-131089 google chrome: Stack-based Buffer Overflow

no score yet

google chrome: no CVSS score yet.

Buffer overflow in CrashReporting in Google Chrome on on Windows prior to 158.0.8127.36 allowed a local attacker who had compromised the renderer process to execute arbitrary code outside the sandbox via a local program. (Chromium security severity: High)
CWE
CWE-121 Stack-based Buffer Overflow
Published
Modified
Assigned by
Chrome (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-131089 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-131089?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-131089?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-131089 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Google Chromefrom 158.0.8127.36 before 158.0.8127.36

References

Check your stackJSON