<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - AWS Lambda - News</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ AWS Lambda News feed</description>
    <item>
      <title>A Trailing Slash Bypassed AWS API Gateway Authorization</title>
      <link>https://www.infoq.com/news/2026/06/aws-api-gateway-auth-bypass/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=AWS+Lambda-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/06/aws-api-gateway-auth-bypass/en/headerimage/generatedHeaderImage-1779890404425.jpg"/&gt;&lt;p&gt;A security researcher found that adding a trailing slash to AWS HTTP API paths bypassed Lambda authorizer authentication entirely, enabling unauthenticated wire transfers at a fintech. The root cause is a path normalization mismatch between HTTP API's greedy route matching and its authorization layer. The same vulnerability class appeared in gRPC-Go via CVE-2026-33186.&lt;/p&gt; &lt;i&gt;By Steef-Jan Wiggers&lt;/i&gt;</description>
      <category>Cloud</category>
      <category>Application Security</category>
      <category>API Gateway</category>
      <category>AWS Lambda</category>
      <category>AWS</category>
      <category>Security Vulnerabilities</category>
      <category>DevOps</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>news</category>
      <pubDate>Mon, 01 Jun 2026 09:55:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/06/aws-api-gateway-auth-bypass/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=AWS+Lambda-news</guid>
      <dc:creator>Steef-Jan Wiggers</dc:creator>
      <dc:date>2026-06-01T09:55:00Z</dc:date>
      <dc:identifier>/news/2026/06/aws-api-gateway-auth-bypass/en</dc:identifier>
    </item>
  </channel>
</rss>
