[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fzkPUt-z3bd9SPR-yRUpAKOw8yThE1dYIlrvhcAfj4UM":3},{"lesson":4},{"id":5,"slug":6,"article_id":7,"title":8,"body":9,"prevention":10,"framework_refs":11,"framework_notes":17,"status":23,"created_at":24,"published_at":25,"article":26,"tags":30,"podcasts":43,"controls":50},"caa5ed6a-9705-4441-8caa-358c7852dca7","chrome-158-patches-204-flaws-including-six-critical-code-execution-bugs","76d9707a-5a29-491b-9cdd-1805c4140ecf","Chrome 158 Patches 204 Flaws, Including Six Critical Code Execution Bugs","Google's Chrome 158 release addressed 204 vulnerabilities, six of them critical, spanning memory safety issues such as use-after-free bugs and memory errors in core browser components like WebView, GPU, and WebAudio. Memory safety flaws of this type are among the most dangerous classes of vulnerability because they can allow attackers to execute arbitrary code within the context of the browser, potentially compromising the underlying system. While Google reported no active exploitation, unpatched browsers in enterprise environments represent an open attack surface that adversaries routinely probe. Organizations that lack enforced, timely browser update policies are exposed for every day a critical patch goes unapplied.","**Immediate actions:**\n- Update all Chrome installations to build 158.0.8127.36 (Linux) or 158.0.8127.36\u002F37 (Windows\u002FmacOS) immediately.\n- Audit managed endpoints to confirm Chrome version compliance and flag any devices still running older builds.\n\n**Long-term improvements:**\n- Enforce automated browser updates enterprise-wide using a mobile device management (MDM) or group policy solution.\n- Maintain a continuously updated software inventory that tracks browser versions across all endpoints.\n- Establish a risk-based patching SLA (e.g., critical patches applied within 24–72 hours of release).\n\n**Detection measures:**\n- Deploy vulnerability scanning on endpoints to detect outdated browser versions as soon as new patch releases occur.\n- Integrate browser version telemetry into your SIEM to alert on non-compliant devices in near real time.",[12,13,14,15,16],"CIS Control 7: Continuous Vulnerability Management (v8)","CIS Control 2: Inventory and Control of Software Assets (v8)","NIST SP 800-53 SI-2: Flaw Remediation","NIST CSF 2.0 RS.MI-3: Newly identified vulnerabilities are mitigated or documented as accepted risks","NIS2 Article 21(2)(e)",{"NIS2 Article 21(2)(e)":18,"NIST SP 800-53 SI-2: Flaw Remediation":19,"CIS Control 7: Continuous Vulnerability Management (v8)":20,"CIS Control 2: Inventory and Control of Software Assets (v8)":21,"NIST CSF 2.0 RS.MI-3: Newly identified vulnerabilities are mitigated or documented as accepted risks":22},"NIS2 Article 21(2)(e) requires security in acquisition, development, and maintenance including vulnerability handling, meaning organizations must have processes to apply critical browser patches like Chrome 158 promptly.","SI-2 requires organizations to identify, report, and correct information system flaws in a timely manner, directly covering the need to deploy Chrome's critical security patches without delay.","CIS Control 7 requires organizations to continuously assess and remediate vulnerabilities; applying Chrome's critical patches promptly is a direct fulfillment of this control's patching cadence requirements.","CIS Control 2 requires maintaining an accurate software inventory, which is a prerequisite for identifying which endpoints are running vulnerable Chrome versions and need the patch.","This category requires that once critical vulnerabilities such as these Chrome memory flaws are identified, organizations act to mitigate them or formally accept the risk rather than leaving systems unpatched.","published","2026-11-18T11:20:59.49246+00:00","2026-11-18T11:20:59.463+00:00",{"id":7,"url":27,"slug":28,"title":29},"https:\u002F\u002Fcybersecuritynews.com\u002Fchrome-158-fixes-204-vulnerabilities\u002F","chrome-158-fixes-204-vulnerabilities-including-critical-code-execution-flaws-c2814e","Chrome 158 Fixes 204 Vulnerabilities, Including Critical Code Execution Flaws",[31,37],{"id":32,"name":33,"slug":34,"description":35,"color":36},"05757c8d-6b93-4194-b35d-7359e7d33b0e","Vulnerability Management","vulnerability-management","Missing scans, no risk prioritization","#fb923c",{"id":38,"name":39,"slug":40,"description":41,"color":42},"af7fce9e-1ce8-4156-93bc-09dcfbfdf29d","Patch Management","patch-management","Unpatched vulnerabilities, delayed updates","#ef4444",[44],{"id":45,"date":46,"edition":47,"title":48,"audio_url":49},"77cf8b97-7175-4e9a-80b6-02a01b6bdc5b","2026-11-18","afternoon","ThreatNoir Afternoon Brief — November 18","https:\u002F\u002Fcdn.threatnoir.com\u002Fpodcasts\u002F2026-11-18\u002Fthreatnoir-afternoon-brief-2026-11-18.mp3",[51,54,57],{"slug":34,"name":52,"problem":53},"Vulnerability scanning and prioritisation","You know which systems are vulnerable, and which ones to fix first.",{"slug":40,"name":55,"problem":56},"Automated patch management","Known holes get closed in days, not months.",{"slug":58,"name":59,"problem":60},"endpoint-management","Device management (MDM and UEM)","Every company laptop and phone is known, encrypted, locked down and up to date."]