<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Browser-Security on CuraSec</title><link>https://curasec.metacog.co.kr/tags/browser-security/</link><description>Recent content in Browser-Security on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 12 Jul 2026 11:56:34 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/browser-security/index.xml" rel="self" type="application/rss+xml"/><item><title>Chrome CSS zero-day CVE-2026-2441 exploited in the wild</title><link>https://curasec.metacog.co.kr/insights/2026-07-12-zero-day-css-cve-2026-2441-exists-in-the-wild/</link><pubDate>Sun, 12 Jul 2026 11:56:34 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-07-12-zero-day-css-cve-2026-2441-exists-in-the-wild/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Act:&lt;/strong> KEV-listed zero-day actively exploited in Chrome&amp;rsquo;s CSS engine; update Chrome/Chromium to the patched stable release immediately and verify managed browsers in your fleet are on the latest version.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Act:&lt;/strong> Active in-the-wild exploitation means assume-breach posture for any endpoint running unpatched Chrome; hunt for suspicious child processes or unusual network connections from Chrome since the February 2026 stable release date, and check EDR telemetry for exploitation indicators.&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> CISA KEV listing confirms active exploitation of a Chrome browser zero-day; validate that your IT/engineering teams have a forced browser-update mechanism and confirm rollout completion — this is routine but warrants a status check given KEV designation.&lt;/li>
&lt;li>&lt;strong>Signals:&lt;/strong> CVE-2026-2441 — CISA KEV: listed, EPSS 0.22, public PoC on GitHub&lt;/li>
&lt;/ul></description></item></channel></rss>