/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

Google releases a Chrome update that fixes seven vulnerabilities, including two zero-days exploited in the wild

Google has released Chrome 95.0.4638.69 for Windows, Mac, and Linux to fix two zero-day vulnerabilities that attackers have actively exploited.

BleepingComputer Lawrence Abrams

Context & Ripple Effects

Chrome’s security-update arc already included an actively exploited zero-day patch in 2020, followed by another high-severity exploited flaw in 2022. This release adds two exploited flaws to that recurring pattern across Google’s desktop Chrome builds.

Later coverage shows the cadence intensified: Google issued an emergency fix for a fifth exploited Chrome zero-day in 2024 and then a third emergency zero-day patch within a week. The significance is not the total number of fixes, but the repeated need to close vulnerabilities after exploitation has begun.

First-order effects

  • Chrome users on Windows, Mac, and Linux receive fixes for seven vulnerabilities; users who update remove exposure to the two flaws already being exploited.
  • Attackers using the two known zero-days lose those attack paths on Chrome installations that move to version 95.0.4638.69.

Second-order effects

  • Google’s security team must sustain rapid patch development and distribution as exploited flaws recur, rather than treating browser updates as routine feature releases.
  • Organizations running Chrome must prioritize browser-update deployment, because delaying rollout leaves endpoints exposed to vulnerabilities with active exploitation.

Third-order effects

  • The repeated sequence of exploited flaws followed by emergency fixes points to browser security becoming a continuous operational race between discovery, exploitation, and patch adoption.
  • If this pattern persists, the practical security divide will increasingly be between managed fleets that deploy browser updates quickly and endpoints that lag behind the release cadence.

The trend: Chrome security is moving toward a faster, exploitation-driven patch cycle in which update deployment is a core endpoint-defense control.

Discussion

  • @spaceraccoonsec @spaceraccoonsec on x
    0-day detection is maybe more important than discovery these days.. https://twitter.com/...
  • @campuscodi Catalin Cimpanu on x
    Google fixes 15th and 16th Chrome zero-day this year—the most Google has patched in Chrome in any single calendar year since the browser's first release in 2008. https://therecord.media/... -CVE-2021-38000 -CVE-2021-38003 https://chromereleases.googleblog.com/ ... https://twitter…