<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Jwt on CuraSec</title><link>https://curasec.metacog.co.kr/tags/jwt/</link><description>Recent content in Jwt on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 17 Jul 2026 12:06:10 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/jwt/index.xml" rel="self" type="application/rss+xml"/><item><title>n8n JWT Cross-Issuer Flaw Enables Account Takeover on Enterprise</title><link>https://curasec.metacog.co.kr/insights/2026-07-17-n8n-token-exchange-flaw-could-let-attackers-log-in-as-users/</link><pubDate>Fri, 17 Jul 2026 12:06:10 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-07-17-n8n-token-exchange-flaw-could-let-attackers-log-in-as-users/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> Any n8n Enterprise deployment trusting multiple external JWT issuers is exposed to cross-tenant account takeover via &lt;code>iss&lt;/code> claim bypass; patch n8n to the fixed version and audit multi-issuer OIDC/JWT configurations now.&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>