<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Auth-Headers on CuraSec</title><link>https://curasec.metacog.co.kr/tags/auth-headers/</link><description>Recent content in Auth-Headers on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 07 Oct 2026 17:48:59 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/auth-headers/index.xml" rel="self" type="application/rss+xml"/><item><title>origin-scoped-fetch: drops auth headers on cross-origin redirects</title><link>https://curasec.metacog.co.kr/insights/2026-10-07-quietpelican42-origin-scoped-fetch-70/</link><pubDate>Wed, 07 Oct 2026 17:48:59 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-07-quietpelican42-origin-scoped-fetch-70/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> Addresses a real auth-header leakage risk where custom credentials follow HTTP redirects to unexpected origins; worth evaluating if your app issues authenticated server-side or client-side fetches that may redirect. No exploitation signals or active risk — review as a candidate hardening library.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>