[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fIOl9SoOSd9NYqIHZoc05MkMioZx_RdQybQ0JQvVRbP4":3},{"article":4,"iocs":47,"iocs_total":70,"watch_terms":71,"solutions":72,"lesson":151},{"id":5,"title":6,"slug":7,"summary":8,"ai_summary":9,"brief":10,"url":11,"image_url":12,"published_at":13,"ingested_at":14,"relevance_score":15,"entities":16,"category_id":29,"category":30,"article_tags":34},"76d9707a-5a29-491b-9cdd-1805c4140ecf","Chrome 158 Fixes 204 Vulnerabilities, Including Critical Code Execution Flaws","chrome-158-fixes-204-vulnerabilities-including-critical-code-execution-flaws-c2814e","Google began rolling out Chrome 158 to Windows, macOS, and Linux on November 17, 2026, with 204 security fixes. The desktop release notes list six critical memory bugs that could lead to code execution. However, Google did not spell out the impact of each flaw. The patched builds are 158.0.8127.36 for Linux and 158.0.8127.36 or […] The post Chrome 158 Fixes 204 Vulnerabilities, Including Critical Code Execution Flaws appeared first on Cyber Security News.","Google rolled out Chrome 158 on November 17, 2026, addressing 204 vulnerabilities across Windows, macOS, and Linux. Six critical flaws—three use-after-free bugs in WebView, garbage collection, and WebAudio, plus three memory errors in GPU, ANGLE, and Media components—could enable code execution. The patched builds are 158.0.8127.36 for Linux and 158.0.8127.36\u002F37 for Windows\u002FmacOS; Google did not indicate active exploitation of these flaws.","Google releases Chrome 158 with 204 security fixes, including 6 critical code execution flaws.","https:\u002F\u002Fcybersecuritynews.com\u002Fchrome-158-fixes-204-vulnerabilities\u002F","https:\u002F\u002Fcybersecuritynews.com\u002Fwp-content\u002Fuploads\u002F2026\u002F11\u002FChrome-158-Fixes-204-Vulnerabilities-Including-Critical-Code-Execution-Flaws.webp","2026-11-18T10:41:12+00:00","2026-11-18T11:00:25.242339+00:00",9,[17,20,23,25,27],{"name":18,"type":19},"Chrome","product",{"name":21,"type":22},"Google","vendor",{"name":24,"type":19},"V8",{"name":26,"type":19},"ANGLE",{"name":28,"type":22},"Anthropic","80544778-fabb-4dcd-aa35-17492e5dcf4f",{"id":29,"icon":31,"name":32,"slug":33},null,"Vulnerabilities","vulnerabilities",[35,40,45],{"category":36},{"id":37,"icon":31,"name":38,"slug":39},"02371804-cf6d-4449-98de-f1a2d4d9b266","Tools","tools",{"category":41},{"id":42,"icon":31,"name":43,"slug":44},"574f766a-fb3f-487c-8d2c-0720ae75471b","Zero-day","zero-day",{"category":46},{"id":29,"icon":31,"name":32,"slug":33},[48,52,55,58,61,64,67],{"type":49,"value":50,"context":51},"cve","CVE-2026-131060","Critical buffer overflow in Media",{"type":49,"value":53,"context":54},"CVE-2026-131031","Critical out-of-bounds write in GPU component",{"type":49,"value":56,"context":57},"CVE-2026-130975","Critical use-after-free in WebAudio",{"type":49,"value":59,"context":60},"CVE-2026-130910","High-severity failure in ANGLE protection mechanism",{"type":49,"value":62,"context":63},"CVE-2026-131054","Critical out-of-bounds write in ANGLE graphics layer",{"type":49,"value":65,"context":66},"CVE-2026-130963","Critical use-after-free in WebView",{"type":49,"value":68,"context":69},"CVE-2026-131008","Critical use-after-free in garbage collection",7,[21,28,18],{"controls":73,"vendors":145},[74,103,131],{"slug":75,"name":76,"problem":77,"products":78},"vulnerability-management","Vulnerability scanning and prioritisation","You know which systems are vulnerable, and which ones to fix first.",[79,87,95],{"vendor_slug":80,"vendor_name":81,"vendor_logo":82,"product_slug":83,"product_name":84,"url":85,"description":86},"holm-security","Holm Security","\u002Fvendor-logos\u002Fholm-security.png","holm-security-platform","Holm Security Platform","https:\u002F\u002Fwww.holmsecurity.com\u002F","Vulnerability scanning of systems, web applications, cloud and the external attack surface, plus phishing simulation.",{"vendor_slug":88,"vendor_name":89,"vendor_logo":90,"product_slug":91,"product_name":92,"url":93,"description":94},"rapid7","Rapid7","\u002Fvendor-logos\u002Frapid7.png","insightvm","Rapid7 Exposure Command (InsightVM)","https:\u002F\u002Fwww.rapid7.com\u002Fproducts\u002Finsightvm\u002F","Vulnerability scanning and risk-based prioritisation; InsightVM is now part of Exposure Command, alongside attack surface and cloud risk.",{"vendor_slug":96,"vendor_name":97,"vendor_logo":98,"product_slug":99,"product_name":100,"url":101,"description":102},"tenable","Tenable","\u002Fvendor-logos\u002Ftenable.png","tenable-vulnerability-management","Tenable Vulnerability Management","https:\u002F\u002Fwww.tenable.com\u002Fproducts\u002Fvulnerability-management","Cloud-based vulnerability scanning and prioritisation, built on Nessus.",{"slug":104,"name":105,"problem":106,"products":107},"patch-management","Automated patch management","Known holes get closed in days, not months.",[108,116,124],{"vendor_slug":109,"vendor_name":110,"vendor_logo":111,"product_slug":112,"product_name":113,"url":114,"description":115},"microsoft","Microsoft","\u002Fvendor-logos\u002Fmicrosoft.png","intune","Microsoft Intune","https:\u002F\u002Fwww.microsoft.com\u002Fen-us\u002Fsecurity\u002Fbusiness\u002Fmicrosoft-intune","Device management for Windows, macOS, iOS and Android, including update rings and compliance policies.",{"vendor_slug":117,"vendor_name":118,"vendor_logo":119,"product_slug":120,"product_name":121,"url":122,"description":123},"manageengine","ManageEngine","\u002Fvendor-logos\u002Fmanageengine.png","patch-manager-plus","ManageEngine Patch Manager Plus","https:\u002F\u002Fwww.manageengine.com\u002Fpatch-management\u002F","Patch management for operating systems and third-party applications, on premises or in the cloud.",{"vendor_slug":125,"vendor_name":126,"vendor_logo":127,"product_slug":104,"product_name":128,"url":129,"description":130},"qualys","Qualys","\u002Fvendor-logos\u002Fqualys.png","Qualys Patch Management","https:\u002F\u002Fwww.qualys.com\u002Fapps\u002Fpatch-management\u002F","Patch deployment for operating systems and third-party applications, linked to vulnerability findings.",{"slug":132,"name":133,"problem":134,"products":135},"endpoint-management","Device management (MDM and UEM)","Every company laptop and phone is known, encrypted, locked down and up to date.",[136,137],{"vendor_slug":109,"vendor_name":110,"vendor_logo":111,"product_slug":112,"product_name":113,"url":114,"description":115},{"vendor_slug":138,"vendor_name":139,"vendor_logo":140,"product_slug":141,"product_name":142,"url":143,"description":144},"ninjaone","NinjaOne","\u002Fvendor-logos\u002Fninjaone.png","ninjaone-patch-management","NinjaOne Patch Management","https:\u002F\u002Fwww.ninjaone.com\u002Fpatch-management\u002F","Automated patching of operating systems and third-party applications from the cloud.",[146],{"slug":147,"name":21,"logo_path":148,"roles":149},"google","\u002Fvendor-logos\u002Fgoogle.png",[150],"affected",{"slug":152,"title":153,"body":154,"framework_refs":155,"framework_notes":161},"chrome-158-patches-204-flaws-including-six-critical-code-execution-bugs","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.",[156,157,158,159,160],"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)":162,"NIST SP 800-53 SI-2: Flaw Remediation":163,"CIS Control 7: Continuous Vulnerability Management (v8)":164,"CIS Control 2: Inventory and Control of Software Assets (v8)":165,"NIST CSF 2.0 RS.MI-3: Newly identified vulnerabilities are mitigated or documented as accepted risks":166},"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."]