<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Nextjs on CuraSec</title><link>https://curasec.metacog.co.kr/tags/nextjs/</link><description>Recent content in Nextjs on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 27 Aug 2026 21:01:55 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/nextjs/index.xml" rel="self" type="application/rss+xml"/><item><title>Next.js Critical AVIF and Windows Path Traversal RCE Flaws Patched</title><link>https://curasec.metacog.co.kr/insights/2026-08-27-next-js-patches-critical-avif-and-windows-flaws-enabling-una/</link><pubDate>Thu, 27 Aug 2026 21:01:55 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-08-27-next-js-patches-critical-avif-and-windows-flaws-enabling-una/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Act:&lt;/strong> Public PoC on GitHub for unauthenticated RCE in a ubiquitous web framework clears the bar for immediate action — upgrade Next.js to the patched release now, prioritizing any Windows-hosted deployments and any apps accepting untrusted image uploads.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Plan:&lt;/strong> With a public PoC and no KEV listing yet, build detections for suspicious AVIF uploads and Windows-style path traversal sequences (e.g. ..) in HTTP requests targeting Next.js routes before active exploitation begins.&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> Two critical unauthenticated RCE flaws with public PoC in a widely-deployed framework warrant confirming this quarter that your engineering teams have inventoried Next.js usage and applied patches — flag for a status check if any customer-facing apps are affected.&lt;/li>
&lt;li>&lt;strong>Signals:&lt;/strong> CVE-2026-75604 — CISA KEV: not listed, EPSS n/a, public PoC on GitHub&lt;/li>
&lt;/ul></description></item></channel></rss>