<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Chrome-Zero-Day on CuraSec</title><link>https://curasec.metacog.co.kr/tags/chrome-zero-day/</link><description>Recent content in Chrome-Zero-Day on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 09 Sep 2026 15:05:56 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/chrome-zero-day/index.xml" rel="self" type="application/rss+xml"/><item><title>Google patches actively exploited Chrome zero-day (7th this year)</title><link>https://curasec.metacog.co.kr/insights/2026-09-09-google-warns-of-new-chrome-zero-day-bug-exploited-in-attacks/</link><pubDate>Wed, 09 Sep 2026 15:05:56 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-09-09-google-warns-of-new-chrome-zero-day-bug-exploited-in-attacks/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Act:&lt;/strong> Actively exploited Chrome zero-day warrants immediate action — force-update Chrome across all managed endpoints and verify enterprise Chrome update policies are not lagging behind the patched release.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> No IOCs, TTPs, or exploit specifics are available in the summary to build detections around; monitor threat intel feeds for follow-on analysis that may surface behavioral indicators of exploitation.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>