https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 11:04:19 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-10455 EUVD-2026-10455 https://cve.radiocsirt.org/vuln/euvd-2026-10455 https://cve.radiocsirt.org/vuln/fkie_cve-2023-50730 <p>Grackle is a GraphQL server written in functional Scala, built on the Typelevel stack. The GraphQL specification requires that GraphQL fragments must not form cycles, either directly or indirectly. Prior to Grackle version 0.18.0, that requirement wasn&#39;t checked, and queries with cyclic fragments would have been accepted for type checking and compilation. The attempted compilation of such fragments would result in a JVM `StackOverflowError` being thrown. Some knowledge of an applications GraphQL schema would be required to construct such a query, however no knowledge of any application-specific performance or other behavioural characteristics would be needed.</p> <p>Grackle uses the cats-parse library for parsing GraphQL queries. Prior to version 0.18.0, Grackle made use of the cats-parse `recursive` operator. However, `recursive` is not currently stack safe. `recursive` was used in three places in the parser: nested selection sets, nested input values (lists and objects), and nested list type declarations. Consequently, queries with deeply nested selection sets, input values or list types could be constructed which exploited this, causing a JVM `StackOverflowException` to be thrown during parsing. Because this happens very early in query processing, no specific knowledge of an applications GraphQL schema would be required to construct such a query.</p> <p>The possibility of small queries resulting in stack overflow is a potential denial of service vulnerability. This potentially affect…</p> <p>Grackle is a GraphQL server written in functional Scala, built on the Typelevel stack. The GraphQL specification requires that GraphQL fragments must not form cycles, either directly or indirectly. Prior to Grackle version 0.18.0, that requirement wasn&#39;t checked, and queries with cyclic fragments would have been accepted for type checking and compilation. The attempted compilation of such fragments would result in a JVM `StackOverflowError` being thrown. Some knowledge of an applications GraphQL schema would be required to construct such a query, however no knowledge of any application-specific performance or other behavioural characteristics would be needed.</p> <p>Grackle uses the cats-parse library for parsing GraphQL queries. Prior to version 0.18.0, Grackle made use of the cats-parse `recursive` operator. However, `recursive` is not currently stack safe. `recursive` was used in three places in the parser: nested selection sets, nested input values (lists and objects), and nested list type declarations. Consequently, queries with deeply nested selection sets, input values or list types could be constructed which exploited this, causing a JVM `StackOverflowException` to be thrown during parsing. Because this happens very early in query processing, no specific knowledge of an applications GraphQL schema would be required to construct such a query.</p> <p>The possibility of small queries resulting in stack overflow is a potential denial of service vulnerability. This potentially affect…</p> https://cve.radiocsirt.org/vuln/fkie_cve-2023-50730 https://cve.radiocsirt.org/vuln/ghsa-g56x-7j6w-g8r8 <p><strong>Affected:</strong> Maven: org.typelevel:grackle-core_2.13, Maven: org.typelevel:grackle-core_3, Maven: org.typelevel:grackle-core_sjs1_2.13, Maven: org.typelevel:grackle-core_sjs1_3, Maven: org.typelevel:grackle-core_native0.4_2.13, Maven: org.typelevel:grackle-core_native0.4_3, Maven: edu.gemini:gsp-graphql-core_2.13, Maven: edu.gemini:gsp-graphql-core_3, Maven: edu.gemini:gsp-graphql-core_sjs1_2.13, Maven: edu.gemini:gsp-graphql-core_sjs1_3 and 2 more</p> <p>### Impact</p> <p>Prior to this fix, the GraphQL query parsing was vulnerable to `StackOverflowError`s. The possibility of small queries resulting in stack overflow is a potential denial of service vulnerability.</p> <p>This potentially affects all applications using Grackle which have untrusted users.</p> <p>&gt; [!CAUTION] &gt; **No specific knowledge of an application&#39;s GraphQL schema would be required to construct a pathological query.**</p> <p>### Patches The stack overflow issues have been resolved in the v0.18.0 release of Grackle.</p> <p>### Workarounds Users could interpose a sanitizing layer in between untrusted input and Grackle query processing.</p> <p><strong>Affected:</strong> Maven: org.typelevel:grackle-core_2.13, Maven: org.typelevel:grackle-core_3, Maven: org.typelevel:grackle-core_sjs1_2.13, Maven: org.typelevel:grackle-core_sjs1_3, Maven: org.typelevel:grackle-core_native0.4_2.13, Maven: org.typelevel:grackle-core_native0.4_3, Maven: edu.gemini:gsp-graphql-core_2.13, Maven: edu.gemini:gsp-graphql-core_3, Maven: edu.gemini:gsp-graphql-core_sjs1_2.13, Maven: edu.gemini:gsp-graphql-core_sjs1_3 and 2 more</p> <p>### Impact</p> <p>Prior to this fix, the GraphQL query parsing was vulnerable to `StackOverflowError`s. The possibility of small queries resulting in stack overflow is a potential denial of service vulnerability.</p> <p>This potentially affects all applications using Grackle which have untrusted users.</p> <p>&gt; [!CAUTION] &gt; **No specific knowledge of an application&#39;s GraphQL schema would be required to construct a pathological query.**</p> <p>### Patches The stack overflow issues have been resolved in the v0.18.0 release of Grackle.</p> <p>### Workarounds Users could interpose a sanitizing layer in between untrusted input and Grackle query processing.</p> https://cve.radiocsirt.org/vuln/ghsa-g56x-7j6w-g8r8 https://cve.radiocsirt.org/vuln/gsd-2023-50730 gsd-2023-50730 https://cve.radiocsirt.org/vuln/gsd-2023-50730