<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 12:38:15 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-324639</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-324639</link>
      <description>EUVD-2026-324639</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-324639</guid>
    </item>
    <item>
      <title>fkie_cve-2026-47707</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-47707</link>
      <description>&lt;p&gt;Strawberry GraphQL is a library for creating GraphQL APIs. In versions 0.172.0 through0.315.6, the MaxAliasesLimiter extension in Strawberry fails to account for the multiplicative/amplification effect of FragmentSpreadNode. While it correctly counts static aliases within the AST it does not consider how many times a fragments internal aliases are expanded during execution. this allows an attacker to bypass alias limits and force the server to resolve and render a significantly higher number of aliases than allowed, potentially leading to a  dos via resource exhaustion. Version 0.315.7 contains a fix for the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Strawberry GraphQL is a library for creating GraphQL APIs. In versions 0.172.0 through0.315.6, the MaxAliasesLimiter extension in Strawberry fails to account for the multiplicative/amplification effect of FragmentSpreadNode. While it correctly counts static aliases within the AST it does not consider how many times a fragments internal aliases are expanded during execution. this allows an attacker to bypass alias limits and force the server to resolve and render a significantly higher number of aliases than allowed, potentially leading to a  dos via resource exhaustion. Version 0.315.7 contains a fix for the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-47707</guid>
    </item>
    <item>
      <title>GHSA-fr49-mhgj-crfc — Strawberry GraphQL's Bypass of MaxAliasesLimiter via Fragment Spreads leading to GraphQL Alias Amplification</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-fr49-mhgj-crfc</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: strawberry-graphql&lt;/p&gt;
&lt;p&gt;### Summary
The MaxAliasesLimiter extension in Strawberry fails to account for the multiplicative/amplification effect of FragmentSpreadNode. While it correctly counts static aliases within the AST it does not consider how many times a fragments internal aliases are expanded during execution. this allows an attacker to bypass alias limits and force the server to resolve and render a significantly higher number of aliases than allowed, potentially leading to a  dos via resource exhaustion.&lt;/p&gt;
&lt;p&gt;### Details
The current implementation of alias counting in strawberry/extensions/max_aliases.py uses a static approach
```
for selection in selection_set_owner.selection_set.selections: 
    if isinstance(selection, FieldNode) and selection.alias:
        result += 1&lt;/p&gt;
&lt;p&gt;if isinstance(selection, (FieldNode, InlineFragmentNode)) and ~~~:
        result += count_fields_with_alias(selection)
```&lt;/p&gt;
&lt;p&gt;When a FragmentSpread is used multiple times, the actual number of aliases processed by the execution engine is&lt;/p&gt;
&lt;p&gt;**Total Aliases = query aliases + (num of spreads * aliases within fragment)**&lt;/p&gt;
&lt;p&gt;Because Strawberry only performs a static sum of the text, it misses this multiplication&lt;/p&gt;
&lt;p&gt;### PoC
**server code**
```
import strawberry
from fastapi import FastAPI
from strawberry.fastapi import GraphQLRouter
from strawberry.extensions import MaxAliasesLimiter&lt;/p&gt;
&lt;p&gt;@strawberry.type
class User:
    name: str = &amp;#34;GONA&amp;#34;&lt;/p&gt;
&lt;p&gt;@strawberry.type
class Query:
    @strawberry.field
    def user(self) -&amp;gt; User:
        return Us…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: strawberry-graphql&lt;/p&gt;
&lt;p&gt;### Summary
The MaxAliasesLimiter extension in Strawberry fails to account for the multiplicative/amplification effect of FragmentSpreadNode. While it correctly counts static aliases within the AST it does not consider how many times a fragments internal aliases are expanded during execution. this allows an attacker to bypass alias limits and force the server to resolve and render a significantly higher number of aliases than allowed, potentially leading to a  dos via resource exhaustion.&lt;/p&gt;
&lt;p&gt;### Details
The current implementation of alias counting in strawberry/extensions/max_aliases.py uses a static approach
```
for selection in selection_set_owner.selection_set.selections: 
    if isinstance(selection, FieldNode) and selection.alias:
        result += 1&lt;/p&gt;
&lt;p&gt;if isinstance(selection, (FieldNode, InlineFragmentNode)) and ~~~:
        result += count_fields_with_alias(selection)
```&lt;/p&gt;
&lt;p&gt;When a FragmentSpread is used multiple times, the actual number of aliases processed by the execution engine is&lt;/p&gt;
&lt;p&gt;**Total Aliases = query aliases + (num of spreads * aliases within fragment)**&lt;/p&gt;
&lt;p&gt;Because Strawberry only performs a static sum of the text, it misses this multiplication&lt;/p&gt;
&lt;p&gt;### PoC
**server code**
```
import strawberry
from fastapi import FastAPI
from strawberry.fastapi import GraphQLRouter
from strawberry.extensions import MaxAliasesLimiter&lt;/p&gt;
&lt;p&gt;@strawberry.type
class User:
    name: str = &amp;#34;GONA&amp;#34;&lt;/p&gt;
&lt;p&gt;@strawberry.type
class Query:
    @strawberry.field
    def user(self) -&amp;gt; User:
        return Us…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-fr49-mhgj-crfc</guid>
    </item>
    <item>
      <title>PYSEC-2026-2284</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-2284</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: strawberry-graphql&lt;/p&gt;
&lt;p&gt;Strawberry GraphQL is a library for creating GraphQL APIs. In versions 0.172.0 through0.315.6, the MaxAliasesLimiter extension in Strawberry fails to account for the multiplicative/amplification effect of FragmentSpreadNode. While it correctly counts static aliases within the AST it does not consider how many times a fragments internal aliases are expanded during execution. this allows an attacker to bypass alias limits and force the server to resolve and render a significantly higher number of aliases than allowed, potentially leading to a  dos via resource exhaustion. Version 0.315.7 contains a fix for the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: strawberry-graphql&lt;/p&gt;
&lt;p&gt;Strawberry GraphQL is a library for creating GraphQL APIs. In versions 0.172.0 through0.315.6, the MaxAliasesLimiter extension in Strawberry fails to account for the multiplicative/amplification effect of FragmentSpreadNode. While it correctly counts static aliases within the AST it does not consider how many times a fragments internal aliases are expanded during execution. this allows an attacker to bypass alias limits and force the server to resolve and render a significantly higher number of aliases than allowed, potentially leading to a  dos via resource exhaustion. Version 0.315.7 contains a fix for the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-2284</guid>
    </item>
  </channel>
</rss>
