Full research report
Three Recent Chrome Releases Fix 1,442 Flaws, More Than Prior 23 Updates Combined
Executive assessment
CVE-2026-3545 represents a qualitatively significant case study: a CVSS 9.6 sandbox escape that survived in Chrome's codebase for over 13 years before being surfaced by Google's Gemini-powered AI agent harness in early 2026, well ahead of any external discovery or exploitation. The broader 1,442-flaw surge across Chrome 149–151 is not a sign of worsening software quality but rather a direct consequence of AI-accelerated vulnerability discovery outpacing historical manual review rates; the NVD's own 2026 totals (46,872 CVEs through July) reflect this industry-wide trend. No threat actor activity, PoC code, or exploitation evidence has been identified for CVE-2026-3545 specifically, and patching in Chrome 145 preceded the public disclosure lifecycle. The primary residual risk lies with organisations running unmanaged or embedded Chromium-based applications that do not receive automatic updates, and with the structural challenge of sustaining remediation velocity as AI tools continue to accelerate discovery rates beyond engineering capacity.
What happened
Between late June and late July 2026, Google released Chrome versions 149, 150, and 151, collectively patching approximately 1,442 security vulnerabilities — more than all prior 23 Chrome milestones combined. The surge is driven by Google's deployment of Gemini-powered AI agent harnesses that automate vulnerability discovery, triage, and patch generation. Among the notable findings is CVE-2026-3545, a critical sandbox escape in Chrome's Navigation component that had persisted undetected for over 13 years and was patched in Chrome 145 in March 2026. The broader story reflects a structural shift in vulnerability economics: AI tooling is generating bug reports faster than engineering teams can address them.
Affected scope
All Google Chrome installations prior to version 145.0.7632.159 (Windows/Linux) and 145.0.7632.160 (macOS) are affected by CVE-2026-3545. The broader 1,442-flaw remediation encompasses Chrome versions 149, 150, and 151 across all supported platforms. No specific industry sector or organisation has been identified as a targeted victim.
Technical assessment
CVE-2026-3545 is classified as CWE-20 (Improper Input Validation) in Chrome's Navigation component, which manages page transitions and URL processing. Insufficient validation of data during navigation operations could allow a compromised renderer process to escape Chrome's sandbox boundary and access local files on the host system. The attack requires the victim to visit a crafted HTML page (network-based, user-interaction required), but no elevated privileges are needed for the initial foothold. The vulnerability's 13-year residence in the codebase reflects the difficulty of identifying subtle inter-component logic flaws through traditional code review and fuzzing. The AI-discovered nature of this flaw is significant: Google's Gemini harness was trained on historical CVEs and the full Chrome Git history, enabling detection of dormant, non-crash-producing weaknesses that standard fuzz testing would not surface.
Recommended defensive actions
- Update all Chrome installations to version 145.0.7632.159 or later (Windows/Linux) and 145.0.7632.160 or later (macOS) to remediate CVE-2026-3545; ensure Chrome 151 or later is deployed for the broadest current coverage.
- Enable automatic Chrome updates organisation-wide and verify deployment via endpoint management tooling, confirming no endpoints remain on vulnerable versions.
- Monitor Chrome release cadence changes: Google is piloting twice-weekly security releases; subscribe to the Chrome Releases blog to ensure patch timelines remain within your organisation's remediation SLA.
- Review browser isolation and enterprise policy configurations — particularly any settings that expand renderer process permissions or file-system access — to reduce sandbox-escape blast radius.
- Audit third-party Chrome extensions and embedded Chromium-based applications (Electron apps, embedded browser components) as these may not receive automatic updates and may remain on vulnerable versions indefinitely.
Uncertainties and evidence gaps
- CVSS score discrepancy: NVD records 9.6 while at least one secondary source cites 9.8; the NVD figure is used here as the authoritative value.
- The exact patch milestone for CVE-2026-3545 is inconsistently reported: the article states March 2026, the NVD publication date is March 4 2026, but one secondary source places the patch in 'early May in Chrome 145' — the Chrome 145 stable release and fixed build version (145.0.7632.159) are consistent across NVD and CSIRT-CAN, but the precise release month is not directly confirmed from the official Chrome Releases blog due to access limitations.
- No independent exploitation intelligence has been found; it is unknown whether the 13-year codebase presence of CVE-2026-3545 was previously identified or leveraged by any threat actor prior to Google's AI discovery.
- The full list of CVEs within the 1,442-flaw tranche is not publicly enumerated; it is unclear how many of the AI-discovered bugs are individually tracked with CVE identifiers versus being batched internally.
Vulnerability flow
Defender-oriented path reconstructed only from sourced report findings. Unknown stages are omitted.
No confirmed active exploitation or public proof-of-concept code for CVE-2026-3545; the vulnerability was patched in March 2026 before public disclosure.
Investigation began with CVE-2026-3545 as the focal point of a broader story about an unprecedented Chrome patching surge. Primary source verification via NVD confirmed the CVSS 9.6 rating, CWE-20 classification, and March 2026 patch date, while independent reporting from BleepingComputer and SecurityWeek corroborated both the CVE's AI-discovery origin and the 1,442-flaw aggregate across Chrome 149–151. Exploitation and PoC searches returned no evidence of active in-the-wild use or public exploit code, allowing a clear-cut assessment: significant architectural risk that was remediated before external exploitation.
- What is CVE-2026-3545 and what does it affect?Searched for 'CVE-2026-3545 Chrome sandbox escape Navigation component'
CVE-2026-3545 is a CVSS 9.6 insufficient data validation flaw in Chrome's Navigation component fixed in Chrome 145.0.7632.159, published March 4 2026. Multiple secondary sources confirmed the basic description.
why Established the core vulnerability identity and patch anchor before seeking primary-source confirmation.
- Is the overall Chrome 1,442-flaw count independently corroborated?Searched for 'Chrome 149 150 151 security vulnerabilities 1442 flaws 2026'
BleepingComputer, SecurityWeek, PCWorld, and ThaiCERT all reported on the combined fix count across Chrome 149, 150, and 151, with 1,072 in the first two and 370 in Chrome 151.
why Confirmed the aggregate figure from multiple independent outlets, separating the headline claim from the single CVE under investigation.
- What does the NVD record for CVE-2026-3545?Fetched NVD detail page for CVE-2026-3545nvd.nist.gov ↗
NVD confirms CVSS 9.6, CWE-20, affected versions prior to 145.0.7632.159 (Windows/Linux) and 145.0.7632.160 (macOS), publication date March 4 2026, no known exploitation flagged.
why NVD is the authoritative US government vulnerability database; its record resolves the CVSS discrepancy seen in secondary sources and provides the definitive affected-version range.
- Is there active exploitation or a public PoC for CVE-2026-3545?Searched for 'CVE-2026-3545 Chrome exploit PoC proof of concept active exploitation 2026'
No PoC or exploitation evidence found for CVE-2026-3545; results returned unrelated Chrome CVEs (CVE-2026-2441, CVE-2026-11645) as comparators with known active exploitation.
why Absence of results across GitHub, Exploit-DB, and security news sources for this specific CVE supports the SentinelOne and NVD assessments of no known exploitation — a material finding for the risk assessment.
- What does Google's official blog say about the AI-driven patching effort?Fetched Google Security Blog post on Chrome security improvementsblog.google ↗
Google confirms 1,072 bugs across Chrome 149 and 150, references the 13-year-old sandbox escape (Chromium bug 487383169) discovered via Gemini agent harness, and describes plans for dynamic patching and accelerated release cadence.
why Primary source from the vendor; confirms the AI discovery narrative and provides non-CVE internal bug reference for the 13-year flaw, cross-linking to the CVE under investigation.
- Does SecurityWeek provide independent technical detail on CVE-2026-3545?Fetched SecurityWeek article on Google AI uncovering 13-year-old Chrome flawsecurityweek.com ↗
SecurityWeek names CVE-2026-3545 with CVSS 9.8 (slight discrepancy from NVD's 9.6), confirms patch in Chrome 145, confirms no exploitation reported. Provides independent corroboration of the AI discovery narrative.
why Second independent domain confirming the CVE identity and patch; CVSS discrepancy noted but NVD takes precedence as primary authority.
- What does BleepingComputer report about the broader AI bug-hunting campaign?Fetched BleepingComputer article on AI-assisted Chrome vulnerability fixesbleepingcomputer.com ↗
Confirms 1,072 bugs in Chrome 149+150, describes Gemini agent harness evolution from Naptime and Big Sleep projects, notes no specific exploitation status for the AI-discovered bugs.
why Third independent outlet confirming the aggregate figures and AI tooling context, with no exploitation signals emerging — strengthens the no-active-exploitation assessment.
Research coverage
All 68 registered source leaves were evaluated for this run: 59 completed, 0 were unavailable, 2 failed and 7 were disabled. For this story, 3 registered sources supplied useful evidence (1 primary, 2 corroborating, 0 contextual and 0 PoC/exploit references). 56 completed sources contained no matched information for this story.
Complete source-by-source audit 68 sources
| Source | Run result | Value | Why it was useful — or not |
|---|---|---|---|
| The Hacker Newsnews | ok8 records | Primary evidence1 matched items | Published the source report used to frame and date the event. |
| BleepingComputernews | ok7 records | Corroborating1 matched items | Supplied independent analysis opened and verified during focused research. |
| NVDcve | ok900 records | Corroborating1 matched items | Supplied independent analysis opened and verified during focused research. |
| AlienVault OTXdark_web | failed0 records | Failed | The current collection attempt failed; this source cannot support the report. |
| CIRCL CVEcve | ok30 records | Checked — no match | The source completed, but none of its retained records matched this story. |
| CISA Alertsnews | ok empty0 records | Checked — no match | The source completed but returned no records in the collection scope. |
| CISA KEVkev | ok1656 records | Checked — no match | The source completed, but none of its retained records matched this story. |
| Cisco PSIRTvendor_advisory | ok5309 records | Checked — no match | The source completed, but none of its retained records matched this story. |
| Cisco Talosnews | ok empty0 records | Checked — no match | The source completed but returned no records in the collection scope. |
| deepdarkCTI CVE most exploiteddeepdarkcti | ok94 records | Checked — no match | The source completed, but none of its retained records matched this story. |
| deepdarkCTI Discorddeepdarkcti | ok7 records | Checked — no match | The source completed, but none of its retained records matched this story. |
| deepdarkCTI exploitsdeepdarkcti | ok24 records | Checked — no match | The source completed, but none of its retained records matched this story. |
| deepdarkCTI forumsdeepdarkcti | ok260 records | Checked — no match | The source completed, but none of its retained records matched this story. |
| deepdarkCTI malware as a servicedeepdarkcti | ok7 records | Checked — no match | The source completed, but none of its retained records matched this story. |
| deepdarkCTI malware samplesdeepdarkcti | ok3 records | Checked — no match | The source completed, but none of its retained records matched this story. |
| deepdarkCTI marketsdeepdarkcti | ok127 records | Checked — no match | The source completed, but none of its retained records matched this story. |
| deepdarkCTI phishingdeepdarkcti | ok19 records | Checked — no match | The source completed, but none of its retained records matched this story. |
| deepdarkCTI ransomware gangsdeepdarkcti | ok669 records | Checked — no match | The source completed, but none of its retained records matched this story. |
| deepdarkCTI RATsdeepdarkcti | ok1 records | Checked — no match | The source completed, but none of its retained records matched this story. |
| deepdarkCTI Telegram infostealerdeepdarkcti | ok130 records | Checked — no match | The source completed, but none of its retained records matched this story. |
| deepdarkCTI Telegram threat actorsdeepdarkcti | ok1006 records | Checked — no match | The source completed, but none of its retained records matched this story. |
| deepdarkCTI Twitter threat actorsdeepdarkcti | ok39 records | Checked — no match | The source completed, but none of its retained records matched this story. |
| DNSDumpster domain IOC enrichmentresearch | failed0 records | Failed | The current collection attempt failed; this source cannot support the report. |
| Exploit-DBexploit_reference | ok empty0 records | Checked — no match | The source completed but returned no records in the collection scope. |
| FIRST EPSSepss | ok | Checked — no match | The source completed, but none of its retained records matched this story. |
| Fortinet PSIRTvendor_advisory | disabled | Disabled | Disabled in the source registry; no check was attempted. |
| GitHub topic: cveresearch | ok empty0 records | Checked — no match | The source completed but returned no records in the collection scope. |
| GitHub topic: exploitresearch | ok empty0 records | Checked — no match | The source completed but returned no records in the collection scope. |
| GitHub topic: penetration-testingresearch | ok empty0 records | Checked — no match | The source completed but returned no records in the collection scope. |
| GitHub topic: pocresearch | ok empty0 records | Checked — no match | The source completed but returned no records in the collection scope. |
| GitHub topic: vulnerabilityresearch | ok empty0 records | Checked — no match | The source completed but returned no records in the collection scope. |
| GreyNoiseexploit_reference | ok empty0 records | Checked — no match | The source completed but returned no records in the collection scope. |
| KrebsOnSecuritynews | ok empty0 records | Checked — no match | The source completed but returned no records in the collection scope. |
| LinkedIn RSS proxy feeds (disabled)research | disabled | Disabled | Disabled in the source registry; no check was attempted. |
| MalwareBazaardark_web | ok10 records | Checked — no match | The source completed, but none of its retained records matched this story. |
| Mastodon #cveresearch | ok20 records | Checked — no match | The source completed, but none of its retained records matched this story. |
| Mastodon #cybersecurityresearch | ok20 records | Checked — no match | The source completed, but none of its retained records matched this story. |
| Mastodon #exploitresearch | ok13 records | Checked — no match | The source completed, but none of its retained records matched this story. |
| Mastodon #infosecresearch | ok20 records | Checked — no match | The source completed, but none of its retained records matched this story. |
| Mastodon #malwareresearch | ok20 records | Checked — no match | The source completed, but none of its retained records matched this story. |
| Mastodon #ransomwareresearch | ok20 records | Checked — no match | The source completed, but none of its retained records matched this story. |
| Mastodon #threatintelresearch | ok5 records | Checked — no match | The source completed, but none of its retained records matched this story. |
| Mastodon #vulnerabilityresearch | ok20 records | Checked — no match | The source completed, but none of its retained records matched this story. |
| Metasploit module metadataexploit_reference | ok empty0 records | Checked — no match | The source completed but returned no records in the collection scope. |
| Microsoft MSRCvendor_advisory | ok1588 records | Checked — no match | The source completed, but none of its retained records matched this story. |
| Microsoft Securitynews | ok1 records | Checked — no match | The source completed, but none of its retained records matched this story. |
| MISP Galaxyresearch | ok2 records | Checked — no match | The source completed, but none of its retained records matched this story. |
| MISP threat actor galaxyactor | ok0 records | Checked — no match | The source completed, but none of its retained records matched this story. |
| Palo Alto Networks PSIRTvendor_advisory | ok25 records | Checked — no match | The source completed, but none of its retained records matched this story. |
| ProjectDiscovery nuclei templatesexploit_reference | ok empty0 records | Checked — no match | The source completed but returned no records in the collection scope. |
| Rapid7news | ok1 records | Checked — no match | The source completed, but none of its retained records matched this story. |
| Reddit r/AskNetsec (pending API approval)research | disabled | Disabled | Disabled in the source registry; no check was attempted. |
| Reddit r/cybersecurity (pending API approval)research | disabled | Disabled | Disabled in the source registry; no check was attempted. |
| Reddit r/malware (pending API approval)research | disabled | Disabled | Disabled in the source registry; no check was attempted. |
| Reddit r/netsec (pending API approval)research | disabled | Disabled | Disabled in the source registry; no check was attempted. |
| Reddit r/ReverseEngineering (pending API approval)research | disabled | Disabled | Disabled in the source registry; no check was attempted. |
| SANS ISCnews | ok empty0 records | Checked — no match | The source completed but returned no records in the collection scope. |
| Shadowserver public aggregate honeypot observationsexploit_reference | ok empty0 records | Checked — no match | The source completed but returned no records in the collection scope. |
| Shodanresearch | ok1 records | Checked — no match | The source completed, but none of its retained records matched this story. |
| Sigma Rulesresearch | ok empty0 records | Checked — no match | The source completed but returned no records in the collection scope. |
| Sophos IOCsresearch | ok empty0 records | Checked — no match | The source completed but returned no records in the collection scope. |
| ThreatFoxthreat_intelligence | ok100 records | Checked — no match | The source completed, but none of its retained records matched this story. |
| UK NCSCnews | ok empty0 records | Checked — no match | The source completed but returned no records in the collection scope. |
| Unit42 IOCsresearch | ok empty0 records | Checked — no match | The source completed but returned no records in the collection scope. |
| URLhausdark_web | ok10 records | Checked — no match | The source completed, but none of its retained records matched this story. |
| VirusTotal Community IOC enrichmentresearch | ok4 records | Checked — no match | The source completed, but none of its retained records matched this story. |
| VulnCheck KEVkev | ok500 records | Checked — no match | The source completed, but none of its retained records matched this story. |
| Vulnerability Lookupcve | ok30 records | Checked — no match | The source completed, but none of its retained records matched this story. |
Additional verified pages 11 opened outside the registered collection
Vendor & gov advisories2
Official Google release note patching CVE-2026-3545 in Chrome 145.0.7632.159
Government CERT advisory confirming affected versions and patch guidance
Analysis & research4
Independent corroboration of AI-driven mass vulnerability discovery across Chrome 149 and 150
Detailed coverage of CVE-2026-3545 discovery by Gemini-powered agent harness
Primary source from Google describing AI tooling, dynamic patching plans and release cadence changes
Authoritative CVSS 9.6 score, CWE-20 classification, affected version ranges and publication date