<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Next-Js on CuraSec</title><link>https://curasec.metacog.co.kr/tags/next-js/</link><description>Recent content in Next-Js on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 15 Oct 2026 15:35:13 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/next-js/index.xml" rel="self" type="application/rss+xml"/><item><title>Next.js Critical RCE Patches: React Server Components and librsvg</title><link>https://curasec.metacog.co.kr/insights/2026-10-15-next-js-ships-out-of-band-patch-for-two-critical-rce-flaws-i/</link><pubDate>Thu, 15 Oct 2026 15:35:13 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-15-next-js-ships-out-of-band-patch-for-two-critical-rce-flaws-i/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> Two critical RCE flaws in a ubiquitous framework warrant priority patching, but with no KEV listing, public PoC, or active exploitation confirmed, this is urgent-but-scheduled rather than drop-everything. Upgrade Next.js to the patched release and audit any transitive use of the sharp/librsvg stack for SVG processing in other services.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> No IOCs, no confirmed exploitation, and no TTPs to map yet — nothing to hunt or detect today. File awareness of React Server Components and librsvg/SVG processing as future attack surface if exploitation emerges.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>